Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d78cf82bafbd58d7f93de8fb0b5a67950d563e2942aeb4b731c43f44200eb9b

Tx prefix hash: cefd5c45a8eff12df22e1c539cd90b5a3e341d5473848cbe108064e2a8972f1f
Tx public key: a89207596df1d4bfeeb973145bb6bf05d4340f17ba326033123bdce6f82ad299
Timestamp: 1771004018 Timestamp [UTC]: 2026-02-13 17:33:38 Age [y:d:h:m:s]: 00:275:11:47:47
Block: 1477052 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202376 RingCT/type: yes/0
Extra: 01a89207596df1d4bfeeb973145bb6bf05d4340f17ba326033123bdce6f82ad299021100000007f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b7c8498ed46112c1732b6433749ea0cee25a5558c28e9cdab441c8afd1b651a6 0.000600000000 1966364 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": 1477062, "vin": [ { "gen": { "height": 1477052 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7c8498ed46112c1732b6433749ea0cee25a5558c28e9cdab441c8afd1b651a6" } } ], "extra": [ 1, 168, 146, 7, 89, 109, 241, 212, 191, 238, 185, 115, 20, 91, 182, 191, 5, 212, 52, 15, 23, 186, 50, 96, 51, 18, 59, 220, 230, 248, 42, 210, 153, 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: