← previous blocknext block →recent activity
Analyzing
Block #93,856,115
8 transactions · 7 stateful · 2026-08-07 07:07:50 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,856,115 · 8 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8587278…40f5
0x34b655…2a6f
4 touches
1 conflict
0xec653969…3e38
0x34b655…2a6f
4 touches
1 conflict
0xec653969…3e39
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x9068a9bc…86ee
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x477a1ae5…cba1
0x447d2e…e9f5
2 touches
0 conflicts
0x47b829ac…ee29
0x447d2e…e9f5
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 0xe858727889…e540f5
Audit this contract →
← previous block·next block →recent activity