Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec2e7e33bd38b10d71fd322f71473cd6f53302e5ffbd5bf76e355ba6fe6bd50f

Tx prefix hash: 318fe33d4ba921561ac40e9e4ffc5ee225c6fab226160b54ae5c212acffd2368
Tx public key: 12e9f1ca3ba56991f12a62ecf9d17f8f8264a01ba0dac903f8a2f76b45c89f37
Timestamp: 1577422114 Timestamp [UCT]: 2019-12-27 04:48:34 Age [y:d:h:m:s]: 05:011:20:35:35
Block: 32632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1158493 RingCT/type: yes/0
Extra: 0112e9f1ca3ba56991f12a62ecf9d17f8f8264a01ba0dac903f8a2f76b45c89f37021100000056c3a1a09f000000000000000000

1 output(s) for total of 478.495101621000 dcy

stealth address amount amount idx
00: 653a7eda32bf35cd8e3fbb3a120ff8a7ddab7064ae692c20c19a7551f9f59104 478.495101621000 54337 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": 32642, "vin": [ { "gen": { "height": 32632 } } ], "vout": [ { "amount": 478495101621, "target": { "key": "653a7eda32bf35cd8e3fbb3a120ff8a7ddab7064ae692c20c19a7551f9f59104" } } ], "extra": [ 1, 18, 233, 241, 202, 59, 165, 105, 145, 241, 42, 98, 236, 249, 209, 127, 143, 130, 100, 160, 27, 160, 218, 201, 3, 248, 162, 247, 107, 69, 200, 159, 55, 2, 17, 0, 0, 0, 86, 195, 161, 160, 159, 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