← previous blocknext block →recent activity
Analyzing
Block #99,155,804
16 transactions · 16 stateful · 2026-08-25 21:57:14 UTC
Parallelism
88/100
Blocked
19%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,155,804 · 16 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
2w03w15w011w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x713d6ba3…0aef
0x34b655…2a6f
4 touches
1 conflict
0x9fc6ea79…e2dc
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x014afe35…4453
0x065c9d…c394
2 touches
0 conflicts
0x50033f98…ea79
0x065c9d…c394
2 touches
0 conflicts
0x5258a9e2…b732
0x065c9d…c394
2 touches
0 conflicts
0x7595663e…67ce
0x065c9d…c394
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 0x713d6ba3a1…e80aef
Audit this contract →
← previous block·next block →recent activity