Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ad56d3e6f2d5970134d2b70edd477f1d5fbf73eeb34216bfd448b47620a3fc5

Tx prefix hash: 701e74c11a9a9e0a623392a7d98e3e229a3a567e1613c778f7bf467cb2ab48a8
Tx public key: b76470e3672b034f55b4b4a88a79619968ad6ed541d67bc0aa910fe475178415
Timestamp: 1771708928 Timestamp [UTC]: 2026-02-21 21:22:08 Age [y:d:h:m:s]: 00:270:05:52:25
Block: 1482906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198691 RingCT/type: yes/0
Extra: 01b76470e3672b034f55b4b4a88a79619968ad6ed541d67bc0aa910fe475178415021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e8bd2d7ca20c3a130d8aea42a00b6e493a66d41e64693d9762e866bfeec16a24 0.000600000000 1972302 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": 1482916, "vin": [ { "gen": { "height": 1482906 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8bd2d7ca20c3a130d8aea42a00b6e493a66d41e64693d9762e866bfeec16a24" } } ], "extra": [ 1, 183, 100, 112, 227, 103, 43, 3, 79, 85, 180, 180, 168, 138, 121, 97, 153, 104, 173, 110, 213, 65, 214, 123, 192, 170, 145, 15, 228, 117, 23, 132, 21, 2, 17, 0, 0, 0, 1, 228, 245, 25, 63, 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: