Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cad08360935142500edbd3efe6f3e665db1e34f3116f9e80d31815e2a09fdac9

Tx prefix hash: 64767902f4adba09be9e72f616bee7b1edc3b7ffc5572cf3692562b062a462f6
Tx public key: d8c0f87fa45180ca7b167d0807fd99899f7b741923099d7d0f921f56eacaad0a
Timestamp: 1714417297 Timestamp [UCT]: 2024-04-29 19:01:37 Age [y:d:h:m:s]: 01:049:02:51:14
Block: 1011268 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295943 RingCT/type: yes/0
Extra: 01d8c0f87fa45180ca7b167d0807fd99899f7b741923099d7d0f921f56eacaad0a0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82a7630d77a90bbf0437c122f39a033db5f113ad7329612575c37a05937a0bf8 0.600000000000 1473454 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": 1011278, "vin": [ { "gen": { "height": 1011268 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82a7630d77a90bbf0437c122f39a033db5f113ad7329612575c37a05937a0bf8" } } ], "extra": [ 1, 216, 192, 248, 127, 164, 81, 128, 202, 123, 22, 125, 8, 7, 253, 153, 137, 159, 123, 116, 25, 35, 9, 157, 125, 15, 146, 31, 86, 234, 202, 173, 10, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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