Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e899188d88bf2b4ad08eaa084bb6eee235c587e133864803dc304ecbecaaafb

Tx prefix hash: 4518ba1df2a072c870664a8db0b2805ae4eae15c70b33033a10ec032530880e3
Tx public key: a347b3720f6f66344f9cc4d7ed95a27121ea5d96f7a52b497dc1caf4e9b4d34b
Timestamp: 1741225801 Timestamp [UCT]: 2025-03-06 01:50:01 Age [y:d:h:m:s]: 00:006:15:30:24
Block: 1233065 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4768 RingCT/type: yes/0
Extra: 01a347b3720f6f66344f9cc4d7ed95a27121ea5d96f7a52b497dc1caf4e9b4d34b021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3b77a48ff636870f10e3cc314a49d437ac2e84379f26ede768f7a3e9ecef55c 0.600000000000 1719982 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 dinasty-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": 1233075, "vin": [ { "gen": { "height": 1233065 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3b77a48ff636870f10e3cc314a49d437ac2e84379f26ede768f7a3e9ecef55c" } } ], "extra": [ 1, 163, 71, 179, 114, 15, 111, 102, 52, 79, 156, 196, 215, 237, 149, 162, 113, 33, 234, 93, 150, 247, 165, 43, 73, 125, 193, 202, 244, 233, 180, 211, 75, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8