← previous blocknext block →recent activity
Analyzing
Block #93,280,283
11 transactions · 11 stateful · 2026-08-05 06:52:56 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,280,283 · 11 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
2w04w05w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8fe37a3f…4c89
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x144c76c8…8bb4
0x34b655…2a6f
4 touches
1 conflict
0x0f8965bb…e238
0x34b655…2a6f
2 touches
0 conflicts
0x2ffa0115…ed47
0x34b655…2a6f
2 touches
0 conflicts
0x330e34db…2678
0x34b655…2a6f
2 touches
0 conflicts
0x332c1bfe…3b97
0x34b655…2a6f
2 touches
0 conflicts
0x354afb1d…2b3c
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 0x8fe37a3f4a…bf4c89
Audit this contract →
← previous block·next block →recent activity