Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8db89db8162063f8ffe64ce2163c0655b8b8b5289368fb0ddeea9c2396e445f

Tx prefix hash: bd449df22a9c01fb923481fc668e949eb76b9d6f8211ddafb51b298009e8c631
Tx public key: c6c80f70cd7a63b992e08e09dc1fea96caa0cace36fe797edd719796bf1396d8
Timestamp: 1725655701 Timestamp [UCT]: 2024-09-06 20:48:21 Age [y:d:h:m:s]: 00:124:09:00:13
Block: 1104443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88956 RingCT/type: yes/0
Extra: 01c6c80f70cd7a63b992e08e09dc1fea96caa0cace36fe797edd719796bf1396d802110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 829be2d18018bca6221d7f3d632d41b0a6cf40e6b331fa061787ed310e41283f 0.600000000000 1581584 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": 1104453, "vin": [ { "gen": { "height": 1104443 } } ], "vout": [ { "amount": 600000000, "target": { "key": "829be2d18018bca6221d7f3d632d41b0a6cf40e6b331fa061787ed310e41283f" } } ], "extra": [ 1, 198, 200, 15, 112, 205, 122, 99, 185, 146, 224, 142, 9, 220, 31, 234, 150, 202, 160, 202, 206, 54, 254, 121, 126, 221, 113, 151, 150, 191, 19, 150, 216, 2, 17, 0, 0, 0, 7, 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