Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a311cef8b5fbe8b0c537307663c8cda4ad2a5e9e0d6289466063848501bb8252

Tx prefix hash: 1591eb7bdcc693995521b8b7680f3ced90fbd93ffc3adf2626a18bce3b1d3d0b
Tx public key: 742b627e1c42da2f8b4fd20db852e600cd07ba820267016cc41936e70acb9687
Timestamp: 1735049482 Timestamp [UCT]: 2024-12-24 14:11:22 Age [y:d:h:m:s]: 00:089:13:00:41
Block: 1182215 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63757 RingCT/type: yes/0
Extra: 01742b627e1c42da2f8b4fd20db852e600cd07ba820267016cc41936e70acb96870211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ed3458e422f7f80882dfc305d1af4d01dece0c034d9dfe9bf9a9690c75a0f9b 0.600000000000 1668648 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": 1182225, "vin": [ { "gen": { "height": 1182215 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ed3458e422f7f80882dfc305d1af4d01dece0c034d9dfe9bf9a9690c75a0f9b" } } ], "extra": [ 1, 116, 43, 98, 126, 28, 66, 218, 47, 139, 79, 210, 13, 184, 82, 230, 0, 205, 7, 186, 130, 2, 103, 1, 108, 196, 25, 54, 231, 10, 203, 150, 135, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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