Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0ab3538069a531b3e05aa64aabdd1b052137de089b1bcf40005c3ac47f5be65

Tx prefix hash: 651491f0add865e0ac3b648308080bf5807b3be27629e4e7de7862d44bfa526c
Tx public key: ae0777af2310da51cf3f90b9e07a056bd8e52b676db548aca2c2c6b5b00a0d28
Timestamp: 1696114047 Timestamp [UCT]: 2023-09-30 22:47:27 Age [y:d:h:m:s]: 01:199:12:55:04
Block: 859730 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 403667 RingCT/type: yes/0
Extra: 01ae0777af2310da51cf3f90b9e07a056bd8e52b676db548aca2c2c6b5b00a0d280211000000114b8f5122000000000000000000

1 output(s) for total of 0.869676353000 dcy

stealth address amount amount idx
00: fafda49648ae34b51495a267a5dff3d11a5e31265620d3f120cf7329f3ec0f78 0.869676353000 1313972 of 0

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": 859740, "vin": [ { "gen": { "height": 859730 } } ], "vout": [ { "amount": 869676353, "target": { "key": "fafda49648ae34b51495a267a5dff3d11a5e31265620d3f120cf7329f3ec0f78" } } ], "extra": [ 1, 174, 7, 119, 175, 35, 16, 218, 81, 207, 63, 144, 185, 224, 122, 5, 107, 216, 229, 43, 103, 109, 181, 72, 172, 162, 194, 198, 181, 176, 10, 13, 40, 2, 17, 0, 0, 0, 17, 75, 143, 81, 34, 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