Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95719decb2fd4dcde795c628264ec80ae41850f0dbe9b58ff979b79741471b76

Tx prefix hash: 55a375bdd6bcd5ee744f4906b98ff059637e32979d4203d9a7dd2fccd32e1c5a
Tx public key: 9ed978e5a1048f2d2ac1d2e95982970bdda24bc60d538f857ad9210195e119b7
Timestamp: 1743829005 Timestamp [UTC]: 2025-04-05 04:56:45 Age [y:d:h:m:s]: 01:035:22:48:30
Block: 1254607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276922 RingCT/type: yes/0
Extra: 019ed978e5a1048f2d2ac1d2e95982970bdda24bc60d538f857ad9210195e119b70211000000084060f6d2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2f9402942bdc220b1cc7368bd27abeae8e66d8ac53c7384c83f3ce786d69ea67 0.000600000000 1741688 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": 1254617, "vin": [ { "gen": { "height": 1254607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f9402942bdc220b1cc7368bd27abeae8e66d8ac53c7384c83f3ce786d69ea67" } } ], "extra": [ 1, 158, 217, 120, 229, 161, 4, 143, 45, 42, 193, 210, 233, 89, 130, 151, 11, 221, 162, 75, 198, 13, 83, 143, 133, 122, 217, 33, 1, 149, 225, 25, 183, 2, 17, 0, 0, 0, 8, 64, 96, 246, 210, 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: