Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69c7b3e0f228700b2b99dd2a87739bf0519b8db133a9b83667fe7db4d94556ae

Tx prefix hash: 3e6678476c069f13d5505a9ed011ee6678cfc40578cd74b3bf269423b14198e4
Tx public key: 0f8b2f1699cb5285fe895f2890e2d4f5ae0f5289371234c33d3bd0b075c533aa
Timestamp: 1707138697 Timestamp [UCT]: 2024-02-05 13:11:37 Age [y:d:h:m:s]: 00:339:17:58:29
Block: 950916 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243237 RingCT/type: yes/0
Extra: 010f8b2f1699cb5285fe895f2890e2d4f5ae0f5289371234c33d3bd0b075c533aa02110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ada963c47f963a97bbbc56bc4b41c11ebbdb19309291152f47b9c8cfbc092cd 0.600000000000 1409610 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": 950926, "vin": [ { "gen": { "height": 950916 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ada963c47f963a97bbbc56bc4b41c11ebbdb19309291152f47b9c8cfbc092cd" } } ], "extra": [ 1, 15, 139, 47, 22, 153, 203, 82, 133, 254, 137, 95, 40, 144, 226, 212, 245, 174, 15, 82, 137, 55, 18, 52, 195, 61, 59, 208, 176, 117, 197, 51, 170, 2, 17, 0, 0, 0, 9, 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