Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 626f82fecd6e7dde3da86f9702696f7d87a7d7cba61f3093e2d35ea7dc52ef1e

Tx prefix hash: 8f1e4ff2d341cdeddba64f518db347890a179120d6d175c25e0901a1eb829069
Tx public key: dd78f73c24d47f909ebd498c9aeba7f92c679f23b2c7213a776378368e263168
Timestamp: 1731372881 Timestamp [UCT]: 2024-11-12 00:54:41 Age [y:d:h:m:s]: 01:009:20:17:26
Block: 1151746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265467 RingCT/type: yes/0
Extra: 01dd78f73c24d47f909ebd498c9aeba7f92c679f23b2c7213a776378368e2631680211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f00390efb49a523e8d9de18aba5ba5c0a9c9feafbba29d4d15575c6c0c70a3e 0.600000000000 1637327 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": 1151756, "vin": [ { "gen": { "height": 1151746 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f00390efb49a523e8d9de18aba5ba5c0a9c9feafbba29d4d15575c6c0c70a3e" } } ], "extra": [ 1, 221, 120, 247, 60, 36, 212, 127, 144, 158, 189, 73, 140, 154, 235, 167, 249, 44, 103, 159, 35, 178, 199, 33, 58, 119, 99, 120, 54, 142, 38, 49, 104, 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