Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4fc38be3c987e215690bacc855ffc8259e6a03ac24e2b01b95ae9604e6f92c6

Tx prefix hash: e69d981fc60850eb046bd3b486301ef0dac3728543065447e791f302b9d770be
Tx public key: b31f0543063de6e945f8d5d6be2ae10b575e72494c5fa2289a3fd9ccc63a7fa4
Timestamp: 1740204597 Timestamp [UCT]: 2025-02-22 06:09:57 Age [y:d:h:m:s]: 00:228:01:36:22
Block: 1224587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160716 RingCT/type: yes/0
Extra: 01b31f0543063de6e945f8d5d6be2ae10b575e72494c5fa2289a3fd9ccc63a7fa4021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3722528b8e50dac110ba1f494dd1b63bfb238366558364a81d35c5c8d9776123 0.600000000000 1711450 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": 1224597, "vin": [ { "gen": { "height": 1224587 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3722528b8e50dac110ba1f494dd1b63bfb238366558364a81d35c5c8d9776123" } } ], "extra": [ 1, 179, 31, 5, 67, 6, 61, 230, 233, 69, 248, 213, 214, 190, 42, 225, 11, 87, 94, 114, 73, 76, 95, 162, 40, 154, 63, 217, 204, 198, 58, 127, 164, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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