Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: beb855108258c81424807e9f32850325c32708cb6e985d199e8cc5a088452efd

Tx prefix hash: 3feb6f4d6a20a96727f84ca750b93357d89e21e762612c04e5c41c34887b1383
Tx public key: df62d3ce1d21aa25a34e0240136516c7df5f547d9afc9a7d25ec334cd87b6428
Timestamp: 1734209296 Timestamp [UCT]: 2024-12-14 20:48:16 Age [y:d:h:m:s]: 00:104:06:42:43
Block: 1175272 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74292 RingCT/type: yes/0
Extra: 01df62d3ce1d21aa25a34e0240136516c7df5f547d9afc9a7d25ec334cd87b6428021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5dbc09d46a049e6d46eeb924983052c965b8e6bd3742ecca5bb224bce67344e3 0.600000000000 1661527 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": 1175282, "vin": [ { "gen": { "height": 1175272 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5dbc09d46a049e6d46eeb924983052c965b8e6bd3742ecca5bb224bce67344e3" } } ], "extra": [ 1, 223, 98, 211, 206, 29, 33, 170, 37, 163, 78, 2, 64, 19, 101, 22, 199, 223, 95, 84, 125, 154, 252, 154, 125, 37, 236, 51, 76, 216, 123, 100, 40, 2, 17, 0, 0, 0, 7, 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