Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c5665e4e281a571acd69e6491b59e864da6e57be4e5a20300882fc4a602cd2f

Tx prefix hash: cdd137b1900a9e15cd4aa550c9317dcc5b2c57e793f042f1cb4515636f551b59
Tx public key: 8494271ce694c3220c98f04d7cc730027eb0b70289629265a2f69ad9b42e33d6
Timestamp: 1716261814 Timestamp [UCT]: 2024-05-21 03:23:34 Age [y:d:h:m:s]: 01:185:11:12:39
Block: 1026577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391154 RingCT/type: yes/0
Extra: 018494271ce694c3220c98f04d7cc730027eb0b70289629265a2f69ad9b42e33d602110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd68582211699bb1b4cb57bffefae89ce352861fe25d1e3441d0167b6c72f8b3 0.600000000000 1493732 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": 1026587, "vin": [ { "gen": { "height": 1026577 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd68582211699bb1b4cb57bffefae89ce352861fe25d1e3441d0167b6c72f8b3" } } ], "extra": [ 1, 132, 148, 39, 28, 230, 148, 195, 34, 12, 152, 240, 77, 124, 199, 48, 2, 126, 176, 183, 2, 137, 98, 146, 101, 162, 246, 154, 217, 180, 46, 51, 214, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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