Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de3e9d1771a6ede5d394b93cc2ddf5d70b5cbbfc9cda9e024c88d98ba1519dd6

Tx prefix hash: 6ed2dc804f54e0b8202900726178be87e364b69667aee980b96d738c6d19149e
Tx public key: a40c3399f51b70b2db7a6aab7ef1cc73916acd15d744797e3434ade93f4ee5e1
Timestamp: 1700215870 Timestamp [UCT]: 2023-11-17 10:11:10 Age [y:d:h:m:s]: 01:356:03:39:22
Block: 893542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 513427 RingCT/type: yes/0
Extra: 01a40c3399f51b70b2db7a6aab7ef1cc73916acd15d744797e3434ade93f4ee5e1021100000010faf35c9c000000000000000000

1 output(s) for total of 0.671930601000 dcy

stealth address amount amount idx
00: 0d71b69faa5d52740f106b596500e4e3b102ae319504da5203c9b5fe203f26ce 0.671930601000 1349719 of 0

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": 893552, "vin": [ { "gen": { "height": 893542 } } ], "vout": [ { "amount": 671930601, "target": { "key": "0d71b69faa5d52740f106b596500e4e3b102ae319504da5203c9b5fe203f26ce" } } ], "extra": [ 1, 164, 12, 51, 153, 245, 27, 112, 178, 219, 122, 106, 171, 126, 241, 204, 115, 145, 106, 205, 21, 215, 68, 121, 126, 52, 52, 173, 233, 63, 78, 229, 225, 2, 17, 0, 0, 0, 16, 250, 243, 92, 156, 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