Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30dcd711f809c062025edd45234bf58ce177f8b99f3bcdfb7edce4948aa160db

Tx prefix hash: fc8e1b2edcb2609cfcd796809f94cd48bef6ddb7416dca710f6c71c015491d88
Tx public key: 57f082531b17bcadbfdca663fe9f83a29e829c308e886cb3c5d307cd8af91bbf
Timestamp: 1754524946 Timestamp [UCT]: 2025-08-07 00:02:26 Age [y:d:h:m:s]: 00:105:08:16:37
Block: 1341802 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74312 RingCT/type: yes/0
Extra: 0157f082531b17bcadbfdca663fe9f83a29e829c308e886cb3c5d307cd8af91bbf021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a65db82ca1810e36e22d9fd9af4f14db54cf2c44d6fd1aa8c78672684d6870cb 0.600000000000 1829629 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": 1341812, "vin": [ { "gen": { "height": 1341802 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a65db82ca1810e36e22d9fd9af4f14db54cf2c44d6fd1aa8c78672684d6870cb" } } ], "extra": [ 1, 87, 240, 130, 83, 27, 23, 188, 173, 191, 220, 166, 99, 254, 159, 131, 162, 158, 130, 156, 48, 142, 136, 108, 179, 197, 211, 7, 205, 138, 249, 27, 191, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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