← previous blocknext block →recent activity
Analyzing
Block #99,444,052
20 transactions · 19 stateful · 2026-08-26 22:08:02 UTC
Parallelism
75/100
Blocked
26%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,444,052 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w28w09w117w018w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x676207a8…5d7e
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xaf194fc0…796e
0x34b655…2a6f
4 touches
1 conflict
0xd71df4b5…c273
0x34b655…2a6f
4 touches
1 conflict
0xe5e7089a…fb91
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
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
6 conflicts on slot 0x676207a88a…e05d7e
Audit this contract →
← previous block·next block →recent activity