Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43531cd8e7bdb468525f87f8ac0ca1d8449ac0e07a8c0380af5bc5238efb034f

Tx prefix hash: 7eeaeaedd7f6f567cdc725cc6b15fdcd8b38da540bfc307101bdfeb2d1e9f285
Tx public key: 427df2e42e5b6a2345718c7f903c7411b880ef26ff68435fe7c99a22781ffd31
Timestamp: 1735789947 Timestamp [UCT]: 2025-01-02 03:52:27 Age [y:d:h:m:s]: 00:322:21:46:16
Block: 1188329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228289 RingCT/type: yes/0
Extra: 01427df2e42e5b6a2345718c7f903c7411b880ef26ff68435fe7c99a22781ffd31021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ab1b61d7441ed2f275528ed10434eb52d97138f003238481f52a1a37e340a45 0.600000000000 1674830 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": 1188339, "vin": [ { "gen": { "height": 1188329 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ab1b61d7441ed2f275528ed10434eb52d97138f003238481f52a1a37e340a45" } } ], "extra": [ 1, 66, 125, 242, 228, 46, 91, 106, 35, 69, 113, 140, 127, 144, 60, 116, 17, 184, 128, 239, 38, 255, 104, 67, 95, 231, 201, 154, 34, 120, 31, 253, 49, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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