Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1a97c987ceb6c6ce304b1010478cf4e14e09186ce263c7e363dca82823a711e

Tx prefix hash: c9510238ce6a4d83330f672e24df64b3c415fe5c5a7950f368a0266305baa759
Tx public key: cb402a512ecd411e76f8a3ed5bf854d169222f4cde8c7f507efa0b48bec26a14
Timestamp: 1720239142 Timestamp [UCT]: 2024-07-06 04:12:22 Age [y:d:h:m:s]: 01:117:18:33:30
Block: 1059534 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342704 RingCT/type: yes/0
Extra: 01cb402a512ecd411e76f8a3ed5bf854d169222f4cde8c7f507efa0b48bec26a140211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c9f95c642f0ce3e130027acbc7d184538f483803bbfe176a5e94ccafeaabf9f 0.600000000000 1530003 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": 1059544, "vin": [ { "gen": { "height": 1059534 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c9f95c642f0ce3e130027acbc7d184538f483803bbfe176a5e94ccafeaabf9f" } } ], "extra": [ 1, 203, 64, 42, 81, 46, 205, 65, 30, 118, 248, 163, 237, 91, 248, 84, 209, 105, 34, 47, 76, 222, 140, 127, 80, 126, 250, 11, 72, 190, 194, 106, 20, 2, 17, 0, 0, 0, 4, 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