Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 748cfb81537908b74cbedd018108270e19654c9ad901cec5f62e4a4b379078a1

Tx prefix hash: 7cf8441a703b1c1db76bd7b3ab4c2aa54744c9d862a9ddfa65f576942eb3efae
Tx public key: 7ca5e7a1f8b3182a8b6aedfaea97fbfe82f889dbb72332a6a7d4d33ea12c65f1
Timestamp: 1732824175 Timestamp [UCT]: 2024-11-28 20:02:55 Age [y:d:h:m:s]: 00:109:14:22:01
Block: 1163772 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78147 RingCT/type: yes/0
Extra: 017ca5e7a1f8b3182a8b6aedfaea97fbfe82f889dbb72332a6a7d4d33ea12c65f1021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cda3f88b051f59fce0e0f4beb006c5d9794d1b8de1e939c4f2a8f524ee3eec61 0.600000000000 1649441 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": 1163782, "vin": [ { "gen": { "height": 1163772 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cda3f88b051f59fce0e0f4beb006c5d9794d1b8de1e939c4f2a8f524ee3eec61" } } ], "extra": [ 1, 124, 165, 231, 161, 248, 179, 24, 42, 139, 106, 237, 250, 234, 151, 251, 254, 130, 248, 137, 219, 183, 35, 50, 166, 167, 212, 211, 62, 161, 44, 101, 241, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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