Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62f55ec0bd77f05094a7b651ddd7c1401066c70b4a1e277b68302e270b080dba

Tx prefix hash: e79227733cdd889bc72ae245676bbd7accf9d2d8d6806b4e877a1e529a0c90a3
Tx public key: b275c7d8a7ed487aec5f3b5d3886088458e1f8826794abed0376f0a5fdd3fb3e
Timestamp: 1709955780 Timestamp [UCT]: 2024-03-09 03:43:00 Age [y:d:h:m:s]: 01:069:16:40:34
Block: 974291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310831 RingCT/type: yes/0
Extra: 01b275c7d8a7ed487aec5f3b5d3886088458e1f8826794abed0376f0a5fdd3fb3e02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a9b4b4c83d6f4a6477d205f5799e3c4bf32a44f589a06e40935150f1ca94e8d 0.600000000000 1434246 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": 974301, "vin": [ { "gen": { "height": 974291 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a9b4b4c83d6f4a6477d205f5799e3c4bf32a44f589a06e40935150f1ca94e8d" } } ], "extra": [ 1, 178, 117, 199, 216, 167, 237, 72, 122, 236, 95, 59, 93, 56, 134, 8, 132, 88, 225, 248, 130, 103, 148, 171, 237, 3, 118, 240, 165, 253, 211, 251, 62, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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