Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca0129fedbd6266687b03782ebd9ccf810066e9acd0edf1d2c65253ed86095d1

Tx prefix hash: bc581ada796b407053fd3418aea2aa970d5f15bdce695ad96f5ac2d182c7e81c
Tx public key: 845cdec9253a7e2541b2a4ea8a1121f1a1b599e7bdf5d9dbf78d45d71d80b9f3
Timestamp: 1734169517 Timestamp [UCT]: 2024-12-14 09:45:17 Age [y:d:h:m:s]: 00:093:02:45:37
Block: 1174935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66334 RingCT/type: yes/0
Extra: 01845cdec9253a7e2541b2a4ea8a1121f1a1b599e7bdf5d9dbf78d45d71d80b9f30211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf2d90be0c52a37039df41cba07b31bec2e7e53041351868c42b8fa154bdc056 0.600000000000 1661150 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": 1174945, "vin": [ { "gen": { "height": 1174935 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf2d90be0c52a37039df41cba07b31bec2e7e53041351868c42b8fa154bdc056" } } ], "extra": [ 1, 132, 92, 222, 201, 37, 58, 126, 37, 65, 178, 164, 234, 138, 17, 33, 241, 161, 181, 153, 231, 189, 245, 217, 219, 247, 141, 69, 215, 29, 128, 185, 243, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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