← previous blocknext block →recent activity
Analyzing
Block #99,330,314
12 transactions · 10 stateful · 2026-08-26 12:35:13 UTC
Parallelism
83/100
Blocked
20%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,330,314 · 12 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
6w07w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x03ddb5f7…9c21
0x34b655…2a6f
2 touches
0 conflicts
0x0e87de03…8fa8
0x34b655…2a6f
2 touches
0 conflicts
0x1ae9195f…9cb7
0x34b655…2a6f
2 touches
0 conflicts
0x55192654…91fe
0x34b655…2a6f
2 touches
0 conflicts
0x5730679c…b7d3
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity