← previous blocknext block →recent activity
Analyzing
Block #99,255,808
21 transactions · 15 stateful · 2026-08-26 06:20:22 UTC
Parallelism
86/100
Blocked
20%
Avg conflicts / tx
0.14
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,255,808 · 21 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
2w04w18w215w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1db5837f…1264
0x34b655…2a6f
4 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x048bb9d6…be29
0x065c9d…c394
2 touches
0 conflicts
0xb1fc9470…72ca
0x065c9d…c394
2 touches
0 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
2 touches
0 conflicts
0x12530975…a089
0x3bd359…433a
2 touches
0 conflicts
0xb8c65bc7…e8b5
0x3bd359…433a
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 0x1db5837f6b…d01264
Audit this contract →
← previous block·next block →recent activity