Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5eafe33cb5ecb1411823ee1134de89f63a7cf9f4aa032ccf419b3b2776c327c

Tx prefix hash: 2333d72cd188a5c5a1928dcd35245005954fb6437ec21e80e077ead0275b0285
Tx public key: 8d6d51adf8614cce10647e3faef57f9c87475b593050b092cc7b797d86c6323e
Timestamp: 1717317759 Timestamp [UCT]: 2024-06-02 08:42:39 Age [y:d:h:m:s]: 00:303:01:44:03
Block: 1035328 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216582 RingCT/type: yes/0
Extra: 018d6d51adf8614cce10647e3faef57f9c87475b593050b092cc7b797d86c6323e021100000002c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5eaaf18cb3841087f3d4a535d6f26ce55b0c044880f43c03e015791079e8e3bb 0.600000000000 1503849 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": 1035338, "vin": [ { "gen": { "height": 1035328 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5eaaf18cb3841087f3d4a535d6f26ce55b0c044880f43c03e015791079e8e3bb" } } ], "extra": [ 1, 141, 109, 81, 173, 248, 97, 76, 206, 16, 100, 126, 63, 174, 245, 127, 156, 135, 71, 91, 89, 48, 80, 176, 146, 204, 123, 121, 125, 134, 198, 50, 62, 2, 17, 0, 0, 0, 2, 197, 69, 41, 96, 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