Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a43c7d1abb542967751325c4fda07f5cf7cef532856a8f8cbc8dfcaab9c929a

Tx prefix hash: d456f48f29662a6293338caefeb24cbc4d23cb0e26e94dcab1ff6df143502211
Tx public key: 4a330530df656aca5e541cb04adc71e961bda952e106c985b57c831493d94cfd
Timestamp: 1703359073 Timestamp [UCT]: 2023-12-23 19:17:53 Age [y:d:h:m:s]: 01:103:16:30:17
Block: 919592 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335235 RingCT/type: yes/0
Extra: 014a330530df656aca5e541cb04adc71e961bda952e106c985b57c831493d94cfd02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40450cbe0f01dfc5dc159df3718bdd3d75135eae396d476481a6b7afd6e3c074 0.600000000000 1377266 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": 919602, "vin": [ { "gen": { "height": 919592 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40450cbe0f01dfc5dc159df3718bdd3d75135eae396d476481a6b7afd6e3c074" } } ], "extra": [ 1, 74, 51, 5, 48, 223, 101, 106, 202, 94, 84, 28, 176, 74, 220, 113, 233, 97, 189, 169, 82, 225, 6, 201, 133, 181, 124, 131, 20, 147, 217, 76, 253, 2, 17, 0, 0, 0, 2, 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