Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 1cdb8cb39b1e15eae917149ef3514f20c5e4eba74a51e1a3c213dcd4286f6795

Tx prefix hash: 85ff3c714dcf5872e99e6149d238c31c7e405dcc2227301e3aee9b57d87a64de
Tx public key: 7a69ac1e18a841075f3f45c60c437a81ef08e57bbe1404ba09bac80dd6025e9c
Timestamp: 1745982141 Timestamp [UTC]: 2025-04-30 03:02:21 Age [y:d:h:m:s]: 00:317:10:34:08
Block: 1272449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224505 RingCT/type: yes/0
Extra: 017a69ac1e18a841075f3f45c60c437a81ef08e57bbe1404ba09bac80dd6025e9c02110000000101491f88000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1be2e2d81b924c52cf9abc4b2b7d04fd326afe4d2a0e3558a3414a299826f82e 0.000600000000 1759724 of 15 -

Check which outputs belong to given dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1272459, "vin": [ { "gen": { "height": 1272449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1be2e2d81b924c52cf9abc4b2b7d04fd326afe4d2a0e3558a3414a299826f82e" } } ], "extra": [ 1, 122, 105, 172, 30, 24, 168, 65, 7, 95, 63, 69, 198, 12, 67, 122, 129, 239, 8, 229, 123, 190, 20, 4, 186, 9, 186, 200, 13, 214, 2, 94, 156, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369