Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef26ab9678f6ac4814be4cbaa1c5270c06892278b000b9d0f24888c31f0681b1

Tx prefix hash: 935309de9ac25aa9a29624b65b60943a3c4052a5eb41e9916df47b1751e2be39
Tx public key: 5854e85d5b74ef27b581c3a9f5756928a900599c4d3cce0df37e66d9a0194f65
Timestamp: 1718479878 Timestamp [UCT]: 2024-06-15 19:31:18 Age [y:d:h:m:s]: 00:222:21:55:53
Block: 1044967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159461 RingCT/type: yes/0
Extra: 015854e85d5b74ef27b581c3a9f5756928a900599c4d3cce0df37e66d9a0194f65021100000001befa2d88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f186104565564c79479ab9aba6b3d914a57b3ff54bb60d8a46518b8acad3da1d 0.600000000000 1514416 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": 1044977, "vin": [ { "gen": { "height": 1044967 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f186104565564c79479ab9aba6b3d914a57b3ff54bb60d8a46518b8acad3da1d" } } ], "extra": [ 1, 88, 84, 232, 93, 91, 116, 239, 39, 181, 129, 195, 169, 245, 117, 105, 40, 169, 0, 89, 156, 77, 60, 206, 13, 243, 126, 102, 217, 160, 25, 79, 101, 2, 17, 0, 0, 0, 1, 190, 250, 45, 136, 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