Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6804a99cde5a51a11becda474cbe75a4b7df4ec4f47d646f7926a35ac6c4c9d8

Tx prefix hash: d8205a312b6e0ff8c7c3b1ddc1870167afb8cf37dc5f49d2158790ba5c04762e
Tx public key: 960df47f18964fdd87f28a7dfd8b2c9231d06e0f2d7d410eed2ded19dbbdca2c
Timestamp: 1731055570 Timestamp [UCT]: 2024-11-08 08:46:10 Age [y:d:h:m:s]: 00:167:20:09:16
Block: 1149129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119792 RingCT/type: yes/0
Extra: 01960df47f18964fdd87f28a7dfd8b2c9231d06e0f2d7d410eed2ded19dbbdca2c0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 334e2bdf2da757ba9e3ab63bdb7ad4a86ec4f707bddc01ef4cb4c043e5eeda82 0.600000000000 1634134 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": 1149139, "vin": [ { "gen": { "height": 1149129 } } ], "vout": [ { "amount": 600000000, "target": { "key": "334e2bdf2da757ba9e3ab63bdb7ad4a86ec4f707bddc01ef4cb4c043e5eeda82" } } ], "extra": [ 1, 150, 13, 244, 127, 24, 150, 79, 221, 135, 242, 138, 125, 253, 139, 44, 146, 49, 208, 110, 15, 45, 125, 65, 14, 237, 45, 237, 25, 219, 189, 202, 44, 2, 17, 0, 0, 0, 2, 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