← previous blocknext block →recent activity
Analyzing
Block #93,406,247
10 transactions · 8 stateful · 2026-08-05 17:26:15 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,406,247 · 10 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
2w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b96d534…b6b5
0x34b655…2a6f
4 touches
1 conflict
0xbd6941a1…6281
0x34b655…2a6f
4 touches
1 conflict
0x58d6b9cf…7c9e
0x34b655…2a6f
3 touches
1 conflict
0x1c796c6b…064e
0x34b655…2a6f
2 touches
0 conflicts
0x38befc08…20c8
0x34b655…2a6f
2 touches
0 conflicts
0x3ea25e92…a36d
0x34b655…2a6f
2 touches
0 conflicts
0x47f1c421…ce9c
0x34b655…2a6f
2 touches
0 conflicts
0x48108def…d9c1
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 0x2b96d534a5…d0b6b5
Audit this contract →
← previous block·next block →recent activity