Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f784af230d56ae9c39b0a35f6272cb89c1b64f0ba50b39f2376f0dfaca447e96

Tx prefix hash: 477ef10b82a725068410d0de12bcc3bd317f6036cbbb60be94b999b5e98a5955
Tx public key: 455f4806d5c968b708441b15e489a6cf6201e8154b50c0ddabb72a1298b8eb40
Timestamp: 1732093449 Timestamp [UCT]: 2024-11-20 09:04:09 Age [y:d:h:m:s]: 01:013:03:54:38
Block: 1157714 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267867 RingCT/type: yes/0
Extra: 01455f4806d5c968b708441b15e489a6cf6201e8154b50c0ddabb72a1298b8eb400211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a00fecb21e8da0500ed9a5b6ed5e351a2d21f8966d87ade5a9814b8c764fcae 0.600000000000 1643337 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": 1157724, "vin": [ { "gen": { "height": 1157714 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a00fecb21e8da0500ed9a5b6ed5e351a2d21f8966d87ade5a9814b8c764fcae" } } ], "extra": [ 1, 69, 95, 72, 6, 213, 201, 104, 183, 8, 68, 27, 21, 228, 137, 166, 207, 98, 1, 232, 21, 75, 80, 192, 221, 171, 183, 42, 18, 152, 184, 235, 64, 2, 17, 0, 0, 0, 9, 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