← previous blocknext block →recent activity
Analyzing
Block #93,879,065
33 transactions · 30 stateful · 2026-08-07 09:03:12 UTC
Parallelism
94/100
Blocked
3%
Avg conflicts / tx
0.03
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,879,065 · 33 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
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x4bc1abab…5874
0x34b655…2a6f
3 touches
1 conflict
0xe4e2ed0a…a2ef
0x34b655…2a6f
3 touches
1 conflict
0x0aa54240…f89e
0x34b655…2a6f
2 touches
0 conflicts
0x12d581a6…c9e6
0x34b655…2a6f
2 touches
0 conflicts
0x2fdf6342…9756
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 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity