Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14e5400b068a27a4c05d578df87bf0114baa63e1ad0a69d9d236e5bd0e1a0dea

Tx prefix hash: 403d4e9def34bed8f80d395b42b2b97cb83efafbef24a736677ea9b6597bae2c
Tx public key: 8277ffa9b4f6e9e861399e83010a7e1d96a7ccb8b807ee668c602388cc2c0406
Timestamp: 1717016319 Timestamp [UCT]: 2024-05-29 20:58:39 Age [y:d:h:m:s]: 00:290:19:00:45
Block: 1032823 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207836 RingCT/type: yes/0
Extra: 018277ffa9b4f6e9e861399e83010a7e1d96a7ccb8b807ee668c602388cc2c04060211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7382eda4ec4a552731f4767f3d96b8d279d2dc62c70e1dc8a98cd4044db085f 0.600000000000 1501278 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": 1032833, "vin": [ { "gen": { "height": 1032823 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7382eda4ec4a552731f4767f3d96b8d279d2dc62c70e1dc8a98cd4044db085f" } } ], "extra": [ 1, 130, 119, 255, 169, 180, 246, 233, 232, 97, 57, 158, 131, 1, 10, 126, 29, 150, 167, 204, 184, 184, 7, 238, 102, 140, 96, 35, 136, 204, 44, 4, 6, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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