← previous blocknext block →recent activity
Analyzing
Block #92,544,290
13 transactions · 13 stateful · 2026-08-02 17:08:19 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,544,290 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w28w211w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6eae156…f526
0x34b655…2a6f
6 touches
3 conflicts
0xe283e878…7262
0x34b655…2a6f
4 touches
1 conflict
0x1b49f420…7fe1
0x34b655…2a6f
4 touches
1 conflict
0x4abaedb1…65b9
0x34b655…2a6f
4 touches
1 conflict
0x784eaad2…d176
0x34b655…2a6f
4 touches
1 conflict
0x784eaad2…d177
0x34b655…2a6f
4 touches
1 conflict
0xa0d3a786…91d9
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
3 conflicts on slot 0xc6eae15637…cef526
Audit this contract →
← previous block·next block →recent activity