← previous blocknext block →recent activity
Analyzing
Block #99,456,900
26 transactions · 19 stateful · 2026-08-26 23:12:43 UTC
Parallelism
88/100
Blocked
32%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,456,900 · 26 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
7w08w09w112w113w014w115w118w019w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4a1
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xbd22d0fc…64fd
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd9722304…6ed0
0x34b655…2a6f
4 touches
1 conflict
0xe97d54c5…ef6f
0x34b655…2a6f
4 touches
1 conflict
0xf21aeb71…92a2
0x34b655…2a6f
4 touches
1 conflict
0xf38a3927…ad62
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 0x7e5ea60ab2…b0c4a1
Audit this contract →
← previous block·next block →recent activity