Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2809d853a1e6f1a11490e448cf3add7478a4d7e2da7dcc474ae23897cb205de

Tx prefix hash: e7a0519452ae0d9c000d74c36864cb95567f5f015dafd3723ddd04f035a13535
Tx public key: d0407736f338dea30498cbf9db637ba9be721c4a9eca736218e3f6d0e1e5e19d
Timestamp: 1729707137 Timestamp [UCT]: 2024-10-23 18:12:17 Age [y:d:h:m:s]: 00:140:17:07:51
Block: 1138001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100375 RingCT/type: yes/0
Extra: 01d0407736f338dea30498cbf9db637ba9be721c4a9eca736218e3f6d0e1e5e19d0211000000161f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b56a3bd2ba89743432cfd0070274f14bb73053600aeb453a5474aaaf1f5ad338 0.600000000000 1621598 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": 1138011, "vin": [ { "gen": { "height": 1138001 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b56a3bd2ba89743432cfd0070274f14bb73053600aeb453a5474aaaf1f5ad338" } } ], "extra": [ 1, 208, 64, 119, 54, 243, 56, 222, 163, 4, 152, 203, 249, 219, 99, 123, 169, 190, 114, 28, 74, 158, 202, 115, 98, 24, 227, 246, 208, 225, 229, 225, 157, 2, 17, 0, 0, 0, 22, 31, 10, 83, 235, 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