Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a66dc13ab4561141a506e8849d9abad4d55044f5321d019e5bc288aab0b5b2c9

Tx prefix hash: a66581d7ee99cde167350adc1de8a76f986875f5249e07e3dd4e0483238d372a
Tx public key: dd2af6a216c3de24d3a4f80825cdbc91c03f4f4096cf4b19da5174647801f7d0
Timestamp: 1703744981 Timestamp [UCT]: 2023-12-28 06:29:41 Age [y:d:h:m:s]: 01:118:19:02:41
Block: 922794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346026 RingCT/type: yes/0
Extra: 01dd2af6a216c3de24d3a4f80825cdbc91c03f4f4096cf4b19da5174647801f7d00211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7c35a6a7763a4c944ee5daf413218256a4ab5654d075a4d2595142add63caa9 0.600000000000 1380498 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": 922804, "vin": [ { "gen": { "height": 922794 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7c35a6a7763a4c944ee5daf413218256a4ab5654d075a4d2595142add63caa9" } } ], "extra": [ 1, 221, 42, 246, 162, 22, 195, 222, 36, 211, 164, 248, 8, 37, 205, 188, 145, 192, 63, 79, 64, 150, 207, 75, 25, 218, 81, 116, 100, 120, 1, 247, 208, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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