Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e04d0b75cbf2392d4f05019698abc6423518fbcd90b516e95173618fb35739b

Tx prefix hash: 03fe3ceebca0112e02d69df7aa154d4a9ff38b5f505bc8228f25d9b3c32649e4
Tx public key: 511e6883d28d75ebb0976f9c9d5acd52798b57126eb5db16e1b41cff4b084037
Timestamp: 1727819489 Timestamp [UCT]: 2024-10-01 21:51:29 Age [y:d:h:m:s]: 00:053:16:11:43
Block: 1122389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38346 RingCT/type: yes/0
Extra: 01511e6883d28d75ebb0976f9c9d5acd52798b57126eb5db16e1b41cff4b08403702110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6dc5cbdae93b469902cc5194c52c38b79302b1aac39f194fd00748810660f3c7 0.600000000000 1604816 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": 1122399, "vin": [ { "gen": { "height": 1122389 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6dc5cbdae93b469902cc5194c52c38b79302b1aac39f194fd00748810660f3c7" } } ], "extra": [ 1, 81, 30, 104, 131, 210, 141, 117, 235, 176, 151, 111, 156, 157, 90, 205, 82, 121, 139, 87, 18, 110, 181, 219, 22, 225, 180, 28, 255, 75, 8, 64, 55, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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