Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5076d29679ace16461ca91bae4b8fc07c68cfa7b397f76ca56e691d161bfc519

Tx prefix hash: eda56a0e09d93a718b4d596f51e9caaedcef41303a736f5e5d349f4a313a6068
Tx public key: 67b905c5b06c219010da2431e5caa0f34b11cf30242db286a8ef1e78e2934e19
Timestamp: 1733139366 Timestamp [UCT]: 2024-12-02 11:36:06 Age [y:d:h:m:s]: 00:116:20:44:25
Block: 1166383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83322 RingCT/type: yes/0
Extra: 0167b905c5b06c219010da2431e5caa0f34b11cf30242db286a8ef1e78e2934e19021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64cef21534d160ef03d569d3c19958d82786c3bc0d22fadb35c610f9b01fda11 0.600000000000 1652070 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": 1166393, "vin": [ { "gen": { "height": 1166383 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64cef21534d160ef03d569d3c19958d82786c3bc0d22fadb35c610f9b01fda11" } } ], "extra": [ 1, 103, 185, 5, 197, 176, 108, 33, 144, 16, 218, 36, 49, 229, 202, 160, 243, 75, 17, 207, 48, 36, 45, 178, 134, 168, 239, 30, 120, 226, 147, 78, 25, 2, 17, 0, 0, 0, 3, 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