Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ce6fafc4d383dd24297aa73d29e693118ce9d4f14558ba75b244b8b8e6e330e

Tx prefix hash: a1e771e657412c1469fe6681d02e73efbe1cce0205e8ff6192f8089fe1ffd9be
Tx public key: 71636ab6f742c6cfc95e2a89c33452d8eee3dc91dd998c2d483ccb958bd74a82
Timestamp: 1721989899 Timestamp [UCT]: 2024-07-26 10:31:39 Age [y:d:h:m:s]: 00:255:16:53:44
Block: 1074052 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182647 RingCT/type: yes/0
Extra: 0171636ab6f742c6cfc95e2a89c33452d8eee3dc91dd998c2d483ccb958bd74a82021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5ef7e2711fe3b3eec5d9dd03699c4af30187eac1e97a3e9c2c02a14f4c0fb63 0.600000000000 1546565 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": 1074062, "vin": [ { "gen": { "height": 1074052 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5ef7e2711fe3b3eec5d9dd03699c4af30187eac1e97a3e9c2c02a14f4c0fb63" } } ], "extra": [ 1, 113, 99, 106, 182, 247, 66, 198, 207, 201, 94, 42, 137, 195, 52, 82, 216, 238, 227, 220, 145, 221, 153, 140, 45, 72, 60, 203, 149, 139, 215, 74, 130, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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