Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6a877cf5cf3d7326b42c5a571864bfd9bb42d2780f4e78a16f12631dca7ce0c

Tx prefix hash: 8c0d01880e532c9f52d17f0e0bf88ec7c92c988e8331ecd74495aa1a6bc2d676
Tx public key: 879778ecdba011a9e8b6a0d98e6e76d58f840b378d339bf87759c34193016708
Timestamp: 1609287556 Timestamp [UCT]: 2020-12-30 00:19:16 Age [y:d:h:m:s]: 04:306:23:00:53
Block: 171740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1230511 RingCT/type: yes/0
Extra: 01879778ecdba011a9e8b6a0d98e6e76d58f840b378d339bf87759c3419301670802110000009f57f0ba47000000000000000000

1 output(s) for total of 165.559745669000 dcy

stealth address amount amount idx
00: da7a7b15a5cec64ac9c4d10fb0308beb432ca46b07b50dbeb1c4126e81056793 165.559745669000 323931 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": 171750, "vin": [ { "gen": { "height": 171740 } } ], "vout": [ { "amount": 165559745669, "target": { "key": "da7a7b15a5cec64ac9c4d10fb0308beb432ca46b07b50dbeb1c4126e81056793" } } ], "extra": [ 1, 135, 151, 120, 236, 219, 160, 17, 169, 232, 182, 160, 217, 142, 110, 118, 213, 143, 132, 11, 55, 141, 51, 155, 248, 119, 89, 195, 65, 147, 1, 103, 8, 2, 17, 0, 0, 0, 159, 87, 240, 186, 71, 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