← previous blocknext block →recent activity
Analyzing
Block #99,202,923
15 transactions · 12 stateful · 2026-08-26 01:54:17 UTC
Parallelism
87/100
Blocked
42%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,202,923 · 15 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
1w03w17w09w110w112w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe188ad90…d23f
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0xefeb7937…c283
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x130e6564…c565
0x34b655…2a6f
4 touches
1 conflict
0x244298ba…c7b9
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
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 0xe188ad90a8…5bd23f
Audit this contract →
← previous block·next block →recent activity