Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5273d3368bb66730f0515b15c0c61154d086414a801d6b10fb0e147e278c993

Tx prefix hash: 90c4e8619b209118a272425297b3a75a70f49cd0f51d08c7491265dee250fbd6
Tx public key: 4c6b672862b2c8ad299f5209949062476b016b307c78c0e8fe865cdaca12a313
Timestamp: 1735133904 Timestamp [UCT]: 2024-12-25 13:38:24 Age [y:d:h:m:s]: 00:093:05:35:12
Block: 1182909 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66413 RingCT/type: yes/0
Extra: 014c6b672862b2c8ad299f5209949062476b016b307c78c0e8fe865cdaca12a3130211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29d0518a8014dc57d5dd230d541d021ddd7b335d67f7999e38eb86a3f6ecf4a4 0.600000000000 1669348 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": 1182919, "vin": [ { "gen": { "height": 1182909 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29d0518a8014dc57d5dd230d541d021ddd7b335d67f7999e38eb86a3f6ecf4a4" } } ], "extra": [ 1, 76, 107, 103, 40, 98, 178, 200, 173, 41, 159, 82, 9, 148, 144, 98, 71, 107, 1, 107, 48, 124, 120, 192, 232, 254, 134, 92, 218, 202, 18, 163, 19, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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