Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9fe9fd6cb268be9a28941e8d5edba60ed6f524da572bb48c43a013cf30cfdea6

Tx prefix hash: 442a23f2a40193456a4d1317abea0c14a9e01805fba01687f90ec642b29aa322
Tx public key: eed2e04af012d01990bd4a2b53f190f3b3ab78801cac83c1fead9c84e7a95049
Timestamp: 1711124007 Timestamp [UCT]: 2024-03-22 16:13:27 Age [y:d:h:m:s]: 01:254:00:30:54
Block: 983991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 440253 RingCT/type: yes/0
Extra: 01eed2e04af012d01990bd4a2b53f190f3b3ab78801cac83c1fead9c84e7a9504902110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31c3908549c6e7862764e9917a01240dbc2d8f9e02bd7b684d336c2f7716d6a8 0.600000000000 1444144 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": 984001, "vin": [ { "gen": { "height": 983991 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31c3908549c6e7862764e9917a01240dbc2d8f9e02bd7b684d336c2f7716d6a8" } } ], "extra": [ 1, 238, 210, 224, 74, 240, 18, 208, 25, 144, 189, 74, 43, 83, 241, 144, 243, 179, 171, 120, 128, 28, 172, 131, 193, 254, 173, 156, 132, 231, 169, 80, 73, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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