Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11719a1d63d59dad25a30e49590f71a4d79ac55b851e3cb8846ccc60c262349d

Tx prefix hash: d033ca033b5435027c7784ab083b6eda8d29a76bf9beed63fd1f7ed993889a93
Tx public key: 395143c903c9ae7ed0d898c4a72e13ec3aa2005bed5d08a091d318af98653df3
Timestamp: 1724356378 Timestamp [UCT]: 2024-08-22 19:52:58 Age [y:d:h:m:s]: 00:093:20:07:52
Block: 1093683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67113 RingCT/type: yes/0
Extra: 01395143c903c9ae7ed0d898c4a72e13ec3aa2005bed5d08a091d318af98653df3021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e644716c188502118be60a62325b1d65a5d30bb43d2c8c55269d9feb3fc6e05d 0.600000000000 1568674 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": 1093693, "vin": [ { "gen": { "height": 1093683 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e644716c188502118be60a62325b1d65a5d30bb43d2c8c55269d9feb3fc6e05d" } } ], "extra": [ 1, 57, 81, 67, 201, 3, 201, 174, 126, 208, 216, 152, 196, 167, 46, 19, 236, 58, 162, 0, 91, 237, 93, 8, 160, 145, 211, 24, 175, 152, 101, 61, 243, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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