← previous blocknext block →recent activity
Analyzing
Block #99,154,309
15 transactions · 15 stateful · 2026-08-25 21:49:43 UTC
Parallelism
80/100
Blocked
40%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,154,309 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w26w08w29w110w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd2e7a5c…188f
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x59b52a3d…67c0
0x34b655…2a6f
4 touches
1 conflict
0x7c68d10b…8386
0x34b655…2a6f
4 touches
1 conflict
0x9c2fc330…0091
0x34b655…2a6f
4 touches
1 conflict
0xccebf5c5…8758
0x34b655…2a6f
4 touches
1 conflict
0xd7443f37…eb79
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 0xfd2e7a5ce0…0a188f
Audit this contract →
← previous block·next block →recent activity