← previous blocknext block →recent activity
Analyzing
Block #93,573,149
16 transactions · 16 stateful · 2026-08-06 07:25:18 UTC
Parallelism
63/100
Blocked
38%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,573,149 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w06w09w310w411w514w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8218911e…3bed
0x34b655…2a6f
8 touches
6 conflicts
0x71237fb9…c99c
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x2ec6a4bc…c7ba
0x34b655…2a6f
6 touches
3 conflicts
0xfc4fcaeb…022c
0x34b655…2a6f
6 touches
3 conflicts
0xa35509fa…5cb3
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x8218911eb6…d93bed
Audit this contract →
← previous block·next block →recent activity