Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36d978971af7a17c8306c4853cd8c7118c5f88ec8eb3eb5cc21b4aa62354acaa

Tx prefix hash: a75daf3174cf5112948e955f9f5b085f584c5d97da5d9ee2a4284b8a12149d65
Tx public key: 97667cab006604e3e109c62380aac2e692dbaeba89ef692a85cdb40d4d2a1f7f
Timestamp: 1713666436 Timestamp [UCT]: 2024-04-21 02:27:16 Age [y:d:h:m:s]: 01:038:00:11:58
Block: 1005040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288144 RingCT/type: yes/0
Extra: 0197667cab006604e3e109c62380aac2e692dbaeba89ef692a85cdb40d4d2a1f7f0211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ec36771f90e1d3e98b08421e2713263bd9e7425aeb5e521c2fb8c0e69164d17 0.600000000000 1465618 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": 1005050, "vin": [ { "gen": { "height": 1005040 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ec36771f90e1d3e98b08421e2713263bd9e7425aeb5e521c2fb8c0e69164d17" } } ], "extra": [ 1, 151, 102, 124, 171, 0, 102, 4, 227, 225, 9, 198, 35, 128, 170, 194, 230, 146, 219, 174, 186, 137, 239, 105, 42, 133, 205, 180, 13, 77, 42, 31, 127, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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