Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 015de7ba5e6dc7aa314bd23fab7959c99f0bb887d2897820d0659161858074a1

Tx prefix hash: 6df1d07684f9e4523eb529a8f3a3c6a3b93d66829cf6a1d4d7e340e0ef256aad
Tx public key: d8b8f74fbad2f6624cbc547080374defa72f522821b2f06df939b9c3cef9e85c
Timestamp: 1718914050 Timestamp [UCT]: 2024-06-20 20:07:30 Age [y:d:h:m:s]: 01:202:00:38:17
Block: 1048546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 403032 RingCT/type: yes/0
Extra: 01d8b8f74fbad2f6624cbc547080374defa72f522821b2f06df939b9c3cef9e85c02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c706b62e6b45158f3a007886c9fb1a843d7dc712217900b79bf743a1c26291ef 0.600000000000 1518631 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": 1048556, "vin": [ { "gen": { "height": 1048546 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c706b62e6b45158f3a007886c9fb1a843d7dc712217900b79bf743a1c26291ef" } } ], "extra": [ 1, 216, 184, 247, 79, 186, 210, 246, 98, 76, 188, 84, 112, 128, 55, 77, 239, 167, 47, 82, 40, 33, 178, 240, 109, 249, 57, 185, 195, 206, 249, 232, 92, 2, 17, 0, 0, 0, 1, 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