Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 647968dc6c4aa37fe908e869d657fcb6e3d0beb01920fa0c19557897f22d2f3f

Tx prefix hash: 4d5aa727ace27a353ae678f628fdb16bf43b033194ed845affe468d4f49cd41d
Tx public key: dd88a87c84231d8493ea16dafb5a0c64f564d612adf4cbc5c3b81d6bf4118395
Timestamp: 1729028513 Timestamp [UCT]: 2024-10-15 21:41:53 Age [y:d:h:m:s]: 00:223:01:02:07
Block: 1132407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159222 RingCT/type: yes/0
Extra: 01dd88a87c84231d8493ea16dafb5a0c64f564d612adf4cbc5c3b81d6bf411839502110000001c3cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e76431bab7419650797165cf0d69b764de8bb3f1458c487b8acb30c473fdf912 0.600000000000 1615322 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": 1132417, "vin": [ { "gen": { "height": 1132407 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e76431bab7419650797165cf0d69b764de8bb3f1458c487b8acb30c473fdf912" } } ], "extra": [ 1, 221, 136, 168, 124, 132, 35, 29, 132, 147, 234, 22, 218, 251, 90, 12, 100, 245, 100, 214, 18, 173, 244, 203, 197, 195, 184, 29, 107, 244, 17, 131, 149, 2, 17, 0, 0, 0, 28, 60, 208, 252, 6, 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