Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09cfa4ddacb8a16dab92284eb177221125e89a98909ad005c7480af69fc64f8d

Tx prefix hash: 3c9fd1f5fefdfc8ad1f4067f94cace72dae30ad4ae17bc55b4309adc505e3d2e
Tx public key: 49c7f5af4d74e7fe6d81487d89c3eb6cd6b9042d28c1f02ccf1bb650302146f8
Timestamp: 1736944481 Timestamp [UCT]: 2025-01-15 12:34:41 Age [y:d:h:m:s]: 00:154:11:09:40
Block: 1197883 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110091 RingCT/type: yes/0
Extra: 0149c7f5af4d74e7fe6d81487d89c3eb6cd6b9042d28c1f02ccf1bb650302146f80211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71344aa5d6746ecf9dba497a390c048f7e1c13b1405875337c14ba2703b931fa 0.600000000000 1684500 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": 1197893, "vin": [ { "gen": { "height": 1197883 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71344aa5d6746ecf9dba497a390c048f7e1c13b1405875337c14ba2703b931fa" } } ], "extra": [ 1, 73, 199, 245, 175, 77, 116, 231, 254, 109, 129, 72, 125, 137, 195, 235, 108, 214, 185, 4, 45, 40, 193, 240, 44, 207, 27, 182, 80, 48, 33, 70, 248, 2, 17, 0, 0, 0, 1, 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