← previous blocknext block →recent activity
Analyzing
Block #99,113,449
12 transactions · 9 stateful · 2026-08-25 18:24:02 UTC
Parallelism
83/100
Blocked
44%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,113,449 · 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
2w03w16w17w08w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09d55be1…b65c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xd08db6ee…a943
0x40c49f…2af0
4 touches
1 conflict
0xd1203697…1ae0
0x40c49f…2af0
4 touches
1 conflict
0x53278058…b79b
0x40c49f…2af0
3 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 0x09d55be1f4…2ab65c
Audit this contract →
← previous block·next block →recent activity