Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09ab31a6518f768f39b83d7d3494e224810f7d78edc0556edfd1f0caa8a48771

Tx prefix hash: 29239a88488a7c501a60ed571a29f6a375119614df024191c156766e6772f25f
Tx public key: 0c3c5cd3e2ee2388ced77efd610adb823b29a9c750263b188cb60c007c6f209c
Timestamp: 1715926221 Timestamp [UCT]: 2024-05-17 06:10:21 Age [y:d:h:m:s]: 00:330:10:32:39
Block: 1023791 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236179 RingCT/type: yes/0
Extra: 010c3c5cd3e2ee2388ced77efd610adb823b29a9c750263b188cb60c007c6f209c02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27a5b822d1390e5274256f7dd5c9203a700db843f6609ec9acabd8e453c7447d 0.600000000000 1489026 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": 1023801, "vin": [ { "gen": { "height": 1023791 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27a5b822d1390e5274256f7dd5c9203a700db843f6609ec9acabd8e453c7447d" } } ], "extra": [ 1, 12, 60, 92, 211, 226, 238, 35, 136, 206, 215, 126, 253, 97, 10, 219, 130, 59, 41, 169, 199, 80, 38, 59, 24, 140, 182, 12, 0, 124, 111, 32, 156, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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