← previous blocknext block →recent activity
Analyzing
Block #93,682,094
10 transactions · 9 stateful · 2026-08-06 16:32:59 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,682,094 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31f6cdda…d22b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x6719a767…9d62
0x34b655…2a6f
4 touches
1 conflict
0x2bad40ae…0523
0x34b655…2a6f
4 touches
1 conflict
0x41f1e2e5…2edf
0x34b655…2a6f
2 touches
0 conflicts
0x4767551b…43c4
0x34b655…2a6f
2 touches
0 conflicts
0x7f2ce433…0664
0x34b655…2a6f
2 touches
0 conflicts
0x803eb45d…00bd
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 0x31f6cdda59…dad22b
Audit this contract →
← previous block·next block →recent activity