Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3be2e953138c609d6abb5d6a4f00ce08b019e81df77a78e4d56636aac6fbef4e

Tx prefix hash: d69488903924b073f73e72cd519140595cb9ebc6941c9af73c8586aaf67ac98e
Tx public key: 047ecdefb1c66e76a51d6362cc59e1e0222c66a57f62289a37de5a2f75f1931c
Timestamp: 1771389063 Timestamp [UTC]: 2026-02-18 04:31:03 Age [y:d:h:m:s]: 00:272:16:45:18
Block: 1480234 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200416 RingCT/type: yes/0
Extra: 01047ecdefb1c66e76a51d6362cc59e1e0222c66a57f62289a37de5a2f75f1931c021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: db21301178d6463c50ca840e0328edafd447e29575db1f951db4b5d0bf4c9d76 0.000600000000 1969602 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": 1480244, "vin": [ { "gen": { "height": 1480234 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db21301178d6463c50ca840e0328edafd447e29575db1f951db4b5d0bf4c9d76" } } ], "extra": [ 1, 4, 126, 205, 239, 177, 198, 110, 118, 165, 29, 99, 98, 204, 89, 225, 224, 34, 44, 102, 165, 127, 98, 40, 154, 55, 222, 90, 47, 117, 241, 147, 28, 2, 17, 0, 0, 0, 2, 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: