Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08dfd774f53073a2673d9ffd8377495524c80e9c3ea392c136eb5be627545b86

Tx prefix hash: 41a3a99f3865c65545f5dc73ac9532f38474356ccf830927e622dd85bbd3f84f
Tx public key: b6d9c8ab6a9ffd856db2274340744fb0701d2f48da61b7d8eac3adfc6639cfee
Timestamp: 1713152487 Timestamp [UCT]: 2024-04-15 03:41:27 Age [y:d:h:m:s]: 01:032:01:46:53
Block: 1000765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283904 RingCT/type: yes/0
Extra: 01b6d9c8ab6a9ffd856db2274340744fb0701d2f48da61b7d8eac3adfc6639cfee0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6f1e0fa36896f528d88dd6bb842af885c1b727892c21e8b34c38feb47dd9bb9 0.600000000000 1461265 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": 1000775, "vin": [ { "gen": { "height": 1000765 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6f1e0fa36896f528d88dd6bb842af885c1b727892c21e8b34c38feb47dd9bb9" } } ], "extra": [ 1, 182, 217, 200, 171, 106, 159, 253, 133, 109, 178, 39, 67, 64, 116, 79, 176, 112, 29, 47, 72, 218, 97, 183, 216, 234, 195, 173, 252, 102, 57, 207, 238, 2, 17, 0, 0, 0, 5, 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