Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71814b5c685871491a44f62aae16e1bd1fb0e4548212a6f4422c1c0d064c2438

Tx prefix hash: 78a4f38a533be948acfa0a5d4d45e450ebb4af26da44436a80c959b07579de79
Tx public key: d0e9c9cbf46014633f292e703e3404e4f966a0834dc7deddf179f442478aea79
Timestamp: 1722282725 Timestamp [UCT]: 2024-07-29 19:52:05 Age [y:d:h:m:s]: 00:122:00:30:24
Block: 1076482 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87306 RingCT/type: yes/0
Extra: 01d0e9c9cbf46014633f292e703e3404e4f966a0834dc7deddf179f442478aea79021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a4ce0cf774e8178923a92d4a9040d83d8973e8b6485f51317e129bb1316dbdc 0.600000000000 1549019 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": 1076492, "vin": [ { "gen": { "height": 1076482 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a4ce0cf774e8178923a92d4a9040d83d8973e8b6485f51317e129bb1316dbdc" } } ], "extra": [ 1, 208, 233, 201, 203, 244, 96, 20, 99, 63, 41, 46, 112, 62, 52, 4, 228, 249, 102, 160, 131, 77, 199, 222, 221, 241, 121, 244, 66, 71, 138, 234, 121, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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