Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cf07a4506c2ec23bce91bbfcf123a6258ca087859179e0ee80a4f3799d839c0

Tx prefix hash: a2a9f65f3aaffdd65a722e12a7cb4225b17c53e0082bc2f47d3cbf6ec26f21b0
Tx public key: 8cf29393c7471226ff2f1e103023eee61c0dcff5c5efaba31ed4a26fbe3680e6
Timestamp: 1748420345 Timestamp [UCT]: 2025-05-28 08:19:05 Age [y:d:h:m:s]: 00:174:13:53:51
Block: 1292641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122454 RingCT/type: yes/0
Extra: 018cf29393c7471226ff2f1e103023eee61c0dcff5c5efaba31ed4a26fbe3680e602110000000686ae2f0d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82547b03696a8eb1fe5cf0ee2e12637716e9e45f98c3dee3f8f4c90052409075 0.600000000000 1780112 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": 1292651, "vin": [ { "gen": { "height": 1292641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82547b03696a8eb1fe5cf0ee2e12637716e9e45f98c3dee3f8f4c90052409075" } } ], "extra": [ 1, 140, 242, 147, 147, 199, 71, 18, 38, 255, 47, 30, 16, 48, 35, 238, 230, 28, 13, 207, 245, 197, 239, 171, 163, 30, 212, 162, 111, 190, 54, 128, 230, 2, 17, 0, 0, 0, 6, 134, 174, 47, 13, 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