Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8528afd8dad2143d38f3ea97523e19cf2ec4a863f340cd5fb144bd5ff7561552

Tx prefix hash: 323f03b8f8abd5ee0f24ab2d617583349c2a3a3623a2c248c05b337c8e0874a6
Tx public key: ce762d0b89f4b155e55f770e014d95c71b493fd4db160df16f90821c2be708ef
Timestamp: 1709223816 Timestamp [UCT]: 2024-02-29 16:23:36 Age [y:d:h:m:s]: 01:221:09:19:31
Block: 968221 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416898 RingCT/type: yes/0
Extra: 01ce762d0b89f4b155e55f770e014d95c71b493fd4db160df16f90821c2be708ef0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f212e717422e42e7edb14c2fbb4b126251431e6ba571cde5ec800b39caad712c 0.600000000000 1428022 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": 968231, "vin": [ { "gen": { "height": 968221 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f212e717422e42e7edb14c2fbb4b126251431e6ba571cde5ec800b39caad712c" } } ], "extra": [ 1, 206, 118, 45, 11, 137, 244, 177, 85, 229, 95, 119, 14, 1, 77, 149, 199, 27, 73, 63, 212, 219, 22, 13, 241, 111, 144, 130, 28, 43, 231, 8, 239, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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