← previous blocknext block →recent activity
Analyzing
Block #94,477,545
10 transactions · 8 stateful · 2026-08-09 11:29:39 UTC
Parallelism
60/100
Blocked
38%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,477,545 · 10 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
1w03w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc93761d9…cfdf
0x34b655…2a6f
8 touches
6 conflicts
0x3b56f79b…310f
0x34b655…2a6f
6 touches
3 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x7b323b2e…2059
0x34b655…2a6f
4 touches
1 conflict
0xa46242d8…c0a7
0x34b655…2a6f
4 touches
1 conflict
0xa8c5904c…e1a7
0x34b655…2a6f
4 touches
1 conflict
0xaa19f5a3…6248
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 0xc93761d95d…d2cfdf
Audit this contract →
← previous block·next block →recent activity