Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67d0107aa42c7028c6580cf200fb46ac9606c536fd59cfe8704841c2a3cae7d7

Tx prefix hash: 02a309ca6f3d0060ee9326df710a85343eeb36ccf2d543cdcc224aa9d7108d0e
Tx public key: 5f5acf8cebeda74a655e74b9a67952bc63143c3cb9516b94f76b6bc0a2b1a697
Timestamp: 1727838458 Timestamp [UCT]: 2024-10-02 03:07:38 Age [y:d:h:m:s]: 00:057:11:17:45
Block: 1122548 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41066 RingCT/type: yes/0
Extra: 015f5acf8cebeda74a655e74b9a67952bc63143c3cb9516b94f76b6bc0a2b1a69702110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ddf11d444066ff8417f86e508af0d4c0efc199c56c169a81bc1ae113c6e3834 0.600000000000 1605013 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": 1122558, "vin": [ { "gen": { "height": 1122548 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ddf11d444066ff8417f86e508af0d4c0efc199c56c169a81bc1ae113c6e3834" } } ], "extra": [ 1, 95, 90, 207, 140, 235, 237, 167, 74, 101, 94, 116, 185, 166, 121, 82, 188, 99, 20, 60, 60, 185, 81, 107, 148, 247, 107, 107, 192, 162, 177, 166, 151, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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