Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 866e848424ca2dc61e66c3088bd66218ff1bc4266d0d33e8a941bba1f51bb11f

Tx prefix hash: 83edc3381d22e26cf56c8c075505c9399b700b1516f78da5148d84f977a4eba9
Tx public key: 774e3a9d47fd9f0a12fe9622eb644055e76783bd4cb03fa24e5b7e88c15bb100
Timestamp: 1752410434 Timestamp [UCT]: 2025-07-13 12:40:34 Age [y:d:h:m:s]: 00:200:04:24:26
Block: 1324605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141714 RingCT/type: yes/0
Extra: 01774e3a9d47fd9f0a12fe9622eb644055e76783bd4cb03fa24e5b7e88c15bb100021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44e0a50d1a35095477ec15c5a18df16ec99a260c445b0100e68a19ff3c9fd7d0 0.600000000000 1812348 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": 1324615, "vin": [ { "gen": { "height": 1324605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44e0a50d1a35095477ec15c5a18df16ec99a260c445b0100e68a19ff3c9fd7d0" } } ], "extra": [ 1, 119, 78, 58, 157, 71, 253, 159, 10, 18, 254, 150, 34, 235, 100, 64, 85, 231, 103, 131, 189, 76, 176, 63, 162, 78, 91, 126, 136, 193, 91, 177, 0, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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