← previous blocknext block →recent activity
Analyzing
Block #94,855,795
10 transactions · 10 stateful · 2026-08-10 19:13:42 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,855,795 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9e2f667a…6262
0x34b655…2a6f
4 touches
1 conflict
0x4acbdbcf…a8c6
0x34b655…2a6f
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x17bca7cc…643f
0x34b655…2a6f
2 touches
0 conflicts
0x258e45aa…333e
0x34b655…2a6f
2 touches
0 conflicts
0x4e4c2bbd…5b5b
0x34b655…2a6f
2 touches
0 conflicts
0x6416b5d6…830e
0x34b655…2a6f
2 touches
0 conflicts
0x681dd2e1…ce40
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x9e2f667af1…bb6262
Audit this contract →
← previous block·next block →recent activity