Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89763b3dbf45590c749ffc6a1a521a845d9b163d34465f6f8cfd647653ba7463

Tx prefix hash: 007b6ae3579cf716bd194f0971fd00c0144919458cfffdf34f1a47c210fb9073
Tx public key: 8cb65679b26c4e0f2f6c7cba84948bd94661177e3dcd4772b34e617fb3808e09
Timestamp: 1745791833 Timestamp [UCT]: 2025-04-27 22:10:33 Age [y:d:h:m:s]: 00:206:20:45:04
Block: 1270871 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145556 RingCT/type: yes/0
Extra: 018cb65679b26c4e0f2f6c7cba84948bd94661177e3dcd4772b34e617fb3808e090211000000051f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2553f2689eaac35134e9eb5081f47d507952dfe96d3525168ae261a1e46e95f 0.600000000000 1758116 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": 1270881, "vin": [ { "gen": { "height": 1270871 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2553f2689eaac35134e9eb5081f47d507952dfe96d3525168ae261a1e46e95f" } } ], "extra": [ 1, 140, 182, 86, 121, 178, 108, 78, 15, 47, 108, 124, 186, 132, 148, 139, 217, 70, 97, 23, 126, 61, 205, 71, 114, 179, 78, 97, 127, 179, 128, 142, 9, 2, 17, 0, 0, 0, 5, 31, 144, 81, 122, 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