Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aac80e22c674d61bc05a7dc4ace15a5318a779dba4a1d5b34cea4edd4b19c6a2

Tx prefix hash: 9fdbc5e95c99eb1e2f0186ca4fcdc3b7111c48b0e6965981d6c947c06aa6dc45
Tx public key: bdaaf3ee594d2bb6a996561394b69ebc48e84c09b7e956aec9a03182bcd360a5
Timestamp: 1707888908 Timestamp [UCT]: 2024-02-14 05:35:08 Age [y:d:h:m:s]: 01:011:16:43:11
Block: 957138 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269371 RingCT/type: yes/0
Extra: 01bdaaf3ee594d2bb6a996561394b69ebc48e84c09b7e956aec9a03182bcd360a502110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 662d58f3d8de42a3ec3c009375eaf7380e0e1e2a8db30b1b9ed5d7a89016cc28 0.600000000000 1416454 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": 957148, "vin": [ { "gen": { "height": 957138 } } ], "vout": [ { "amount": 600000000, "target": { "key": "662d58f3d8de42a3ec3c009375eaf7380e0e1e2a8db30b1b9ed5d7a89016cc28" } } ], "extra": [ 1, 189, 170, 243, 238, 89, 77, 43, 182, 169, 150, 86, 19, 148, 182, 158, 188, 72, 232, 76, 9, 183, 233, 86, 174, 201, 160, 49, 130, 188, 211, 96, 165, 2, 17, 0, 0, 0, 11, 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