← previous blocknext block →recent activity
Analyzing
Block #94,301,781
10 transactions · 9 stateful · 2026-08-08 20:36:49 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,301,781 · 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
3w04w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x2a9e9bd1…5368
0x2a68ba…90c5
4 touches
1 conflict
0xa89d5ddb…a92c
0xa6afd3…d132
3 touches
1 conflict
0x039728ac…30f2
0x34b655…2a6f
2 touches
0 conflicts
0x3111a64f…eb7f
0x34b655…2a6f
2 touches
0 conflicts
0x331eb8c3…e3de
0x34b655…2a6f
2 touches
0 conflicts
0x4a1f87d2…e64c
0x34b655…2a6f
2 touches
0 conflicts
0x53699236…fede
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 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity