Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63bfb21c4c4ef259f58abe682f0a07aa78762581568d00c51c17516065b378a9

Tx prefix hash: aad5b7e2706240c2bfe9d1ce050d80518f670c23bada4df50022568fea6db31a
Tx public key: 6345e1db9a0ca235f8576cb7ca0ae59dd86f3807cd5dcb244818f926802669ae
Timestamp: 1688479767 Timestamp [UCT]: 2023-07-04 14:09:27 Age [y:d:h:m:s]: 01:308:15:49:11
Block: 796496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 481754 RingCT/type: yes/0
Extra: 016345e1db9a0ca235f8576cb7ca0ae59dd86f3807cd5dcb244818f926802669ae021100000001faf35c9c000000000000000000

1 output(s) for total of 1.408893761000 dcy

stealth address amount amount idx
00: af8a80d6fa1880c8b79484f59980e9579a2e430127a74fcbcdbc5ff65fcd4aed 1.408893761000 1247363 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": 796506, "vin": [ { "gen": { "height": 796496 } } ], "vout": [ { "amount": 1408893761, "target": { "key": "af8a80d6fa1880c8b79484f59980e9579a2e430127a74fcbcdbc5ff65fcd4aed" } } ], "extra": [ 1, 99, 69, 225, 219, 154, 12, 162, 53, 248, 87, 108, 183, 202, 10, 229, 157, 216, 111, 56, 7, 205, 93, 203, 36, 72, 24, 249, 38, 128, 38, 105, 174, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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