Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ac77458a5f669d4e6997cfb53850caf3f14c2a07e143087887be737c888f759

Tx prefix hash: bb20cc00301c629fa853abae2bdcc4d2ae9fc9065b44206ccb0a1c795e909999
Tx public key: de6deffc70eaed3413b68e5a0cf30c677c9dbca3adf3ec756d735ef11e1e0689
Timestamp: 1757079574 Timestamp [UTC]: 2025-09-05 13:39:34 Age [y:d:h:m:s]: 01:076:06:57:52
Block: 1361941 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320980 RingCT/type: yes/0
Extra: 01de6deffc70eaed3413b68e5a0cf30c677c9dbca3adf3ec756d735ef11e1e0689021100000005ad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: dab39378981f29cb0789dcfa2b42b3a5e614a06670df4aa6e2ff9c0e383c5743 0.000600000000 1849964 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": 1361951, "vin": [ { "gen": { "height": 1361941 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dab39378981f29cb0789dcfa2b42b3a5e614a06670df4aa6e2ff9c0e383c5743" } } ], "extra": [ 1, 222, 109, 239, 252, 112, 234, 237, 52, 19, 182, 142, 90, 12, 243, 12, 103, 124, 157, 188, 163, 173, 243, 236, 117, 109, 115, 94, 241, 30, 30, 6, 137, 2, 17, 0, 0, 0, 5, 173, 121, 72, 208, 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: