Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f6c6c07862e1ae84d33b6920f4fe2c0dadd1fc5723f4a68ecad5a6d3fed6168

Tx prefix hash: 784c8d9ba4e1c4a744bdaa09cbff84e201ec84521ddb84e5c444c04d173d08c9
Tx public key: 4b2ecb3fed8924ab5b07a1e8d40fb31eeb725396b1bec8f1ee2bb3b636ef7217
Timestamp: 1729555738 Timestamp [UCT]: 2024-10-22 00:08:58 Age [y:d:h:m:s]: 01:015:00:23:01
Block: 1136738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269110 RingCT/type: yes/0
Extra: 014b2ecb3fed8924ab5b07a1e8d40fb31eeb725396b1bec8f1ee2bb3b636ef72170211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07f2e09a96c64add60b82559df14cacd3f3730a9666ccf02719d086b7e0fe56c 0.600000000000 1620101 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": 1136748, "vin": [ { "gen": { "height": 1136738 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07f2e09a96c64add60b82559df14cacd3f3730a9666ccf02719d086b7e0fe56c" } } ], "extra": [ 1, 75, 46, 203, 63, 237, 137, 36, 171, 91, 7, 161, 232, 212, 15, 179, 30, 235, 114, 83, 150, 177, 190, 200, 241, 238, 43, 179, 182, 54, 239, 114, 23, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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