← previous blocknext block →recent activity
Analyzing
Block #93,242,870
9 transactions · 9 stateful · 2026-08-05 03:44:49 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,242,870 · 9 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe23bb618…13e8
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x475159fe…d427
0x34b655…2a6f
3 touches
1 conflict
0x033cf007…136d
0x34b655…2a6f
2 touches
0 conflicts
0x06ad0dfb…39a2
0x34b655…2a6f
2 touches
0 conflicts
0x1041bcb3…4c7a
0x34b655…2a6f
2 touches
0 conflicts
0x2385516f…eca5
0x34b655…2a6f
2 touches
0 conflicts
0x23ce455e…41ae
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 0xe23bb618e0…3813e8
Audit this contract →
← previous block·next block →recent activity