← previous blocknext block →recent activity
Analyzing
Block #99,332,098
18 transactions · 16 stateful · 2026-08-26 12:44:12 UTC
Parallelism
89/100
Blocked
19%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,332,098 · 18 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
3w05w18w011w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ed7cc0b…ee52
0x34b655…2a6f
4 touches
1 conflict
0x34aea08d…5127
0x34b655…2a6f
4 touches
1 conflict
0x25180879…8191
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x32164862…19d1
0x34b655…2a6f
2 touches
0 conflicts
0x4366b4ef…6293
0x34b655…2a6f
2 touches
0 conflicts
0x489d7033…e8e1
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 0x0ed7cc0b4b…d2ee52
Audit this contract →
← previous block·next block →recent activity