← previous blocknext block →recent activity
Analyzing
Block #99,160,196
16 transactions · 13 stateful · 2026-08-25 22:19:19 UTC
Parallelism
88/100
Blocked
23%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,160,196 · 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
2w03w14w06w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9274f3fa…8963
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xbb97db90…4c93
0xc8689a…ee79
4 touches
1 conflict
0xf3d7a307…4d63
0x065c9d…c394
2 touches
0 conflicts
0xfb6ec3e2…11e0
0x065c9d…c394
2 touches
0 conflicts
0x11258774…9892
0x2a68ba…90c5
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 0x9274f3fa7e…f88963
Audit this contract →
← previous block·next block →recent activity