Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 466f6292b4c098169cfef16ea604fbc1b26c71f2c03f830174e0b817e6d0af6b

Tx prefix hash: ab9a506e16ee43f0c42c64fac0687ba9ec33eddd9f6a671db3afc06df8f712e2
Tx public key: 5a6f304e229709e5cae521e65db87c3d7ba2c464add4a42e62e3f8164dc99e49
Timestamp: 1616150836 Timestamp [UTC]: 2021-03-19 10:47:16 Age [y:d:h:m:s]: 05:061:11:47:47
Block: 221853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1315243 RingCT/type: yes/0
Extra: 015a6f304e229709e5cae521e65db87c3d7ba2c464add4a42e62e3f8164dc99e4902110000003990ec05ad000000000000000000

1 output(s) for total of 0.112956053110 xmr

stealth address amount amount idx tag
00: 1919afb348919558e8f580b359c1af66cf2ba8e1341a8b7216c1932cc03b2ef5 0.112956053110 457493 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": 221863, "vin": [ { "gen": { "height": 221853 } } ], "vout": [ { "amount": 112956053110, "target": { "key": "1919afb348919558e8f580b359c1af66cf2ba8e1341a8b7216c1932cc03b2ef5" } } ], "extra": [ 1, 90, 111, 48, 78, 34, 151, 9, 229, 202, 229, 33, 230, 93, 184, 124, 61, 123, 162, 196, 100, 173, 212, 164, 46, 98, 227, 248, 22, 77, 201, 158, 73, 2, 17, 0, 0, 0, 57, 144, 236, 5, 173, 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: