Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9270efc4862aace8337cd3b69fb3d6b15bb1e79ba9269bb1e9030beaf8a188f3

Tx prefix hash: d8cd22f648fec4f58ff3d5d82cfab37939fd2611a7985ae7717a9ce25e8a3aee
Tx public key: 7f16f4cc2bd2b7fc9962fc1b17f7fb60538c2a3db7ca263d5f0e35d302af126d
Timestamp: 1774540127 Timestamp [UTC]: 2026-03-26 15:48:47 Age [y:d:h:m:s]: 00:238:21:15:09
Block: 1506309 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176399 RingCT/type: yes/0
Extra: 017f16f4cc2bd2b7fc9962fc1b17f7fb60538c2a3db7ca263d5f0e35d302af126d021100000004e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 67ccf541befb1928af15bc2f51cfd57430519ff2dfbcc5b6d378746aac764699 0.000600000000 1996053 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": 1506319, "vin": [ { "gen": { "height": 1506309 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67ccf541befb1928af15bc2f51cfd57430519ff2dfbcc5b6d378746aac764699" } } ], "extra": [ 1, 127, 22, 244, 204, 43, 210, 183, 252, 153, 98, 252, 27, 23, 247, 251, 96, 83, 140, 42, 61, 183, 202, 38, 61, 95, 14, 53, 211, 2, 175, 18, 109, 2, 17, 0, 0, 0, 4, 228, 245, 25, 63, 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) | monero version: