Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7240dda08efc39035cf7730bfa77fdd2b2a9cf5cead9bb79a6fbe090b8c86919

Tx prefix hash: d1f0aaa6fe29780610c5c848cc72d04b69185cffeb730f6846fc1299be5d374e
Tx public key: 103a11cdbea65df0a225a6ca4a385caaef54581ba811476d440283e5cd17d2b6
Timestamp: 1745210275 Timestamp [UTC]: 2025-04-21 04:37:55 Age [y:d:h:m:s]: 01:209:13:09:56
Block: 1266032 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413767 RingCT/type: yes/0
Extra: 01103a11cdbea65df0a225a6ca4a385caaef54581ba811476d440283e5cd17d2b6021100000006dbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d79daf1a24ff59da97ba33bdde3622dab6e4c20e7f280f1c9add229feb4e08dd 0.000600000000 1753247 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": 1266042, "vin": [ { "gen": { "height": 1266032 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d79daf1a24ff59da97ba33bdde3622dab6e4c20e7f280f1c9add229feb4e08dd" } } ], "extra": [ 1, 16, 58, 17, 205, 190, 166, 93, 240, 162, 37, 166, 202, 74, 56, 92, 170, 239, 84, 88, 27, 168, 17, 71, 109, 68, 2, 131, 229, 205, 23, 210, 182, 2, 17, 0, 0, 0, 6, 219, 181, 113, 193, 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: