Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a620cbe2d13eeb9b89f32a6563a2084cc0ec3d9f80d3758a429ff0308262ffe

Tx prefix hash: a0b6946fe2a79728da156cfdbcbb494b6655677707b8ee46b24dde8ca7ac88e1
Tx public key: 023db1dfd3fef38994019cdd3775ce02d9a078569fd248f86a40cd6fc5a04c0e
Timestamp: 1771916066 Timestamp [UTC]: 2026-02-24 06:54:26 Age [y:d:h:m:s]: 00:268:17:30:55
Block: 1484616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197648 RingCT/type: yes/0
Extra: 01023db1dfd3fef38994019cdd3775ce02d9a078569fd248f86a40cd6fc5a04c0e021100000007f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bc1df5b7db13624ca4e96d9408b3160f3bdf0a73f625aeec03a04c1f9181d090 0.000600000000 1974044 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": 1484626, "vin": [ { "gen": { "height": 1484616 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc1df5b7db13624ca4e96d9408b3160f3bdf0a73f625aeec03a04c1f9181d090" } } ], "extra": [ 1, 2, 61, 177, 223, 211, 254, 243, 137, 148, 1, 156, 221, 55, 117, 206, 2, 217, 160, 120, 86, 159, 210, 72, 248, 106, 64, 205, 111, 197, 160, 76, 14, 2, 17, 0, 0, 0, 7, 241, 136, 200, 168, 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: