Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d55bd60a29fb886a55cbdc15c416849de80a765d276a386ee1eb968fe409e7c

Tx prefix hash: 0ecea763cd09769fdbae7f1796f90f4280da51fec19e130fa5db195d1a4f2d82
Tx public key: 918d7247ecf95cc25662b168ca4e2d6d06f6e8b732ee75609f9effc900b0aef9
Timestamp: 1787178323 Timestamp [UTC]: 2026-08-19 22:25:23 Age [y:d:h:m:s]: 00:093:19:22:07
Block: 1617070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 66424 RingCT/type: yes/0
Extra: 01918d7247ecf95cc25662b168ca4e2d6d06f6e8b732ee75609f9effc900b0aef90208930ebbd73b4b0436

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 36a24e4740c7d3825e46fd97d8847643e567c4597b5a952df41e34afa3a5e1c4 0.000600000000 2107090 of 15 <d2>

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": 1617080, "vin": [ { "gen": { "height": 1617070 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "36a24e4740c7d3825e46fd97d8847643e567c4597b5a952df41e34afa3a5e1c4", "view_tag": "d2" } } } ], "extra": [ 1, 145, 141, 114, 71, 236, 249, 92, 194, 86, 98, 177, 104, 202, 78, 45, 109, 6, 246, 232, 183, 50, 238, 117, 96, 159, 158, 255, 201, 0, 176, 174, 249, 2, 8, 147, 14, 187, 215, 59, 75, 4, 54 ], "rct_signatures": { "type": 0 } }


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