Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6d491832a3435d930c1d9776798bba63885c7d45c6608eb3e1ea15e83a7c1cc

Tx prefix hash: d58ed62a88e3c9fed61a6fe0ce82430d459fbe6219dfce825431354915400a6b
Tx public key: c50d42d98a251b21e1d7cf3473862c3710cee4b2ab9643e518553a9fd1205dd8
Timestamp: 1715584618 Timestamp [UCT]: 2024-05-13 07:16:58 Age [y:d:h:m:s]: 00:230:10:35:25
Block: 1020977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164903 RingCT/type: yes/0
Extra: 01c50d42d98a251b21e1d7cf3473862c3710cee4b2ab9643e518553a9fd1205dd802110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d35a1b4454c9929e1492377c5da186d7aaa05165ba3e2c580ef98763d01f1522 0.600000000000 1485124 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": 1020987, "vin": [ { "gen": { "height": 1020977 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d35a1b4454c9929e1492377c5da186d7aaa05165ba3e2c580ef98763d01f1522" } } ], "extra": [ 1, 197, 13, 66, 217, 138, 37, 27, 33, 225, 215, 207, 52, 115, 134, 44, 55, 16, 206, 228, 178, 171, 150, 67, 229, 24, 85, 58, 159, 209, 32, 93, 216, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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