Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59ad3f79878aa38e71eb0d96e36dfdaa0ccdc03574fbef77b5da3b59dad48903

Tx prefix hash: c6af2ada3796ba0953d02d4144e197648a93096b91ff6e2b3d9c07393b28b884
Tx public key: 10e35b3539edb22190920aca88d420cccd6d2ddb036e015c2a5f8d232ccda1b1
Timestamp: 1696105219 Timestamp [UCT]: 2023-09-30 20:20:19 Age [y:d:h:m:s]: 01:223:01:46:22
Block: 859656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 420499 RingCT/type: yes/0
Extra: 0110e35b3539edb22190920aca88d420cccd6d2ddb036e015c2a5f8d232ccda1b102110000000933af99f4000000000000000000

1 output(s) for total of 0.870167491000 dcy

stealth address amount amount idx
00: c03950770d1f9dd7fe8752a3c19e012d0c583201b512962369e538ec5d418620 0.870167491000 1313894 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": 859666, "vin": [ { "gen": { "height": 859656 } } ], "vout": [ { "amount": 870167491, "target": { "key": "c03950770d1f9dd7fe8752a3c19e012d0c583201b512962369e538ec5d418620" } } ], "extra": [ 1, 16, 227, 91, 53, 57, 237, 178, 33, 144, 146, 10, 202, 136, 212, 32, 204, 205, 109, 45, 219, 3, 110, 1, 92, 42, 95, 141, 35, 44, 205, 161, 177, 2, 17, 0, 0, 0, 9, 51, 175, 153, 244, 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