Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee905cd317bbee576766229348a9f8760d4c20de203e3972db16d22713e4d16b

Tx prefix hash: ac1e0aa210ff4e17e4450140f2027e8e1098ddf76761588f0884e90eeed23814
Tx public key: da2f1f034217e5a33749dff7c04f8687e7738c4773a1adade0a5b9618a036368
Timestamp: 1650604081 Timestamp [UTC]: 2022-04-22 05:08:01 Age [y:d:h:m:s]: 04:129:02:07:15
Block: 485462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1137262 RingCT/type: yes/0
Extra: 01da2f1f034217e5a33749dff7c04f8687e7738c4773a1adade0a5b9618a03636802110000000ecb8520c2000000000000000000

1 output(s) for total of 0.015116912384 xmr

stealth address amount amount idx tag
00: 364c8358528cd2fc8fc123e22086d71a88f59caba07de213bb2d84a68c357547 0.015116912384 907537 of 0 -

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": 485472, "vin": [ { "gen": { "height": 485462 } } ], "vout": [ { "amount": 15116912384, "target": { "key": "364c8358528cd2fc8fc123e22086d71a88f59caba07de213bb2d84a68c357547" } } ], "extra": [ 1, 218, 47, 31, 3, 66, 23, 229, 163, 55, 73, 223, 247, 192, 79, 134, 135, 231, 115, 140, 71, 115, 161, 173, 173, 224, 165, 185, 97, 138, 3, 99, 104, 2, 17, 0, 0, 0, 14, 203, 133, 32, 194, 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: