Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dde5904d2657273f6b8954a20d13d70b4d444cd019adefb69a0f0d2cd9e28e67

Tx prefix hash: 54db5dcbef37acaaabc36b132ca9c5de6ddfe0828e81d403692a0c05c49a078e
Tx public key: a65d38cca223fe0f233090623d6be4e9a8e807f4463d5275915949f603dcdd62
Timestamp: 1706284014 Timestamp [UCT]: 2024-01-26 15:46:54 Age [y:d:h:m:s]: 01:137:20:43:14
Block: 943817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359627 RingCT/type: yes/0
Extra: 01a65d38cca223fe0f233090623d6be4e9a8e807f4463d5275915949f603dcdd6202110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 691629db6f05e70789c4e7162891ec37bfaeb9cfe299e19fe901cbcfe50d61ab 0.600000000000 1402043 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": 943827, "vin": [ { "gen": { "height": 943817 } } ], "vout": [ { "amount": 600000000, "target": { "key": "691629db6f05e70789c4e7162891ec37bfaeb9cfe299e19fe901cbcfe50d61ab" } } ], "extra": [ 1, 166, 93, 56, 204, 162, 35, 254, 15, 35, 48, 144, 98, 61, 107, 228, 233, 168, 232, 7, 244, 70, 61, 82, 117, 145, 89, 73, 246, 3, 220, 221, 98, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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