← previous blocknext block →recent activity
Analyzing
Block #99,122,275
20 transactions · 17 stateful · 2026-08-25 19:08:33 UTC
Parallelism
90/100
Blocked
24%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,122,275 · 20 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
5w06w18w011w016w117w018w119w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x676207a8…5d7e
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x33ce2799…dfd1
0x34b655…2a6f
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x2101bec4…84b9
0x34b655…2a6f
4 touches
1 conflict
0x9c140da5…82ff
0x34b655…2a6f
4 touches
1 conflict
0x912b7bc7…1af9
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 0x676207a88a…e05d7e
Audit this contract →
← previous block·next block →recent activity