Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c32a8c8001797c8a3d2d0f9be99044eb56db961115b6623f07c4b4b287665cc

Tx prefix hash: 8c70c0e05767004ee3b4db1bd0d7568e87e863a75a33917005a63c3f5ce7d9d3
Tx public key: da2b537a42f6ae36ba328ab4f95655b365bab0d06f7a7048bbf3b93eedc623e3
Timestamp: 1719734130 Timestamp [UCT]: 2024-06-30 07:55:30 Age [y:d:h:m:s]: 00:319:08:55:19
Block: 1055346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228235 RingCT/type: yes/0
Extra: 01da2b537a42f6ae36ba328ab4f95655b365bab0d06f7a7048bbf3b93eedc623e302110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1151952f831fbb2db53ce57d559f2d0ac30e2ee71e9e32796eca7191943d098 0.600000000000 1525745 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": 1055356, "vin": [ { "gen": { "height": 1055346 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1151952f831fbb2db53ce57d559f2d0ac30e2ee71e9e32796eca7191943d098" } } ], "extra": [ 1, 218, 43, 83, 122, 66, 246, 174, 54, 186, 50, 138, 180, 249, 86, 85, 179, 101, 186, 176, 208, 111, 122, 112, 72, 187, 243, 185, 62, 237, 198, 35, 227, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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