Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91c5473b8f1a216ebcd180219f66e67474600ceb70a9632cf28056e667df7b3e

Tx prefix hash: ac9bddeb6eecd508a4f4b7c26edad516412309a2d37221c6e3ecef5a6f3e9dd9
Tx public key: 23adda34675564bdeb7aeb90d825a8d3926d77501b3abf1070b1eab9e52eef44
Timestamp: 1770383426 Timestamp [UTC]: 2026-02-06 13:10:26 Age [y:d:h:m:s]: 00:281:18:01:39
Block: 1471957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206765 RingCT/type: yes/0
Extra: 0123adda34675564bdeb7aeb90d825a8d3926d77501b3abf1070b1eab9e52eef4402110000000cf188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ca010d7cc3d7986609a291c03fb4473d5fc5096237e85652f346c1414b14c1df 0.000600000000 1961233 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": 1471967, "vin": [ { "gen": { "height": 1471957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca010d7cc3d7986609a291c03fb4473d5fc5096237e85652f346c1414b14c1df" } } ], "extra": [ 1, 35, 173, 218, 52, 103, 85, 100, 189, 235, 122, 235, 144, 216, 37, 168, 211, 146, 109, 119, 80, 27, 58, 191, 16, 112, 177, 234, 185, 229, 46, 239, 68, 2, 17, 0, 0, 0, 12, 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: