← previous blocknext block →recent activity
Analyzing
Block #93,844,337
9 transactions · 9 stateful · 2026-08-07 06:08:38 UTC
Parallelism
56/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,844,337 · 9 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2550f1c1…a0e4
0x34b655…2a6f
4 touches
1 conflict
0xa8b8fbde…396d
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc6f3e65d…79ff
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe33ef400…df49
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
1 conflict on slot 0x2550f1c158…11a0e4
Audit this contract →
← previous block·next block →recent activity