← previous blocknext block →recent activity
Analyzing
Block #93,242,400
16 transactions · 15 stateful · 2026-08-05 03:42:27 UTC
Parallelism
63/100
Blocked
40%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,242,400 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w16w27w38w410w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0358d223…4714
0x34b655…2a6f
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xf9e23360…8ef7
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
4 touches
1 conflict
0x5efd7300…d8a5
0x34b655…2a6f
4 touches
1 conflict
0x6cde3e6d…1238
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
10 conflicts on slot 0x0358d22323…964714
Audit this contract →
← previous block·next block →recent activity