← previous blocknext block →recent activity
Analyzing
Block #94,743,095
12 transactions · 11 stateful · 2026-08-10 09:45:59 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,743,095 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w07w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeef37ed7…3606
0x34b655…2a6f
8 touches
6 conflicts
0x671560e4…1c4f
0x34b655…2a6f
8 touches
6 conflicts
0xdf6c3e51…c493
0x34b655…2a6f
6 touches
3 conflicts
0x0fb9e50c…1a35
0x34b655…2a6f
4 touches
1 conflict
0x35b89cd8…5092
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x706c758c…2fdb
0x34b655…2a6f
4 touches
1 conflict
0xc2b37cdc…e470
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
6 conflicts on slot 0xeef37ed726…cd3606
Audit this contract →
← previous block·next block →recent activity