Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63a38b0dfe7478a4769ee4377374c25df7eb082781c5cc983e2c26b3fe8dc9e2

Tx prefix hash: c903916ded91f0201b9d71aca28860822e09a4ad95b514629ce06b653eb0ecf8
Tx public key: 1cdc09eb963d0a95622584f62b7b66963b830fb7d150434963c4c4c06557a3fa
Timestamp: 1710202296 Timestamp [UCT]: 2024-03-12 00:11:36 Age [y:d:h:m:s]: 01:033:15:34:47
Block: 976340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285034 RingCT/type: yes/0
Extra: 011cdc09eb963d0a95622584f62b7b66963b830fb7d150434963c4c4c06557a3fa0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc5ede35103cd5984fd1312b272ed8a0f09b8ae0a17070d0ec2aebbd28838d8b 0.600000000000 1436333 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": 976350, "vin": [ { "gen": { "height": 976340 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc5ede35103cd5984fd1312b272ed8a0f09b8ae0a17070d0ec2aebbd28838d8b" } } ], "extra": [ 1, 28, 220, 9, 235, 150, 61, 10, 149, 98, 37, 132, 246, 43, 123, 102, 150, 59, 131, 15, 183, 209, 80, 67, 73, 99, 196, 196, 192, 101, 87, 163, 250, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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