← previous blocknext block →recent activity
Analyzing
Block #99,200,200
23 transactions · 23 stateful · 2026-08-26 01:40:35 UTC
Parallelism
91/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,200,200 · 23 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
1w03w16w08w09w122w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09ea36ec…b8c6
0x34b655…2a6f
4 touches
1 conflict
0xd194ae5c…cbc8
0x065c9d…c394
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x4527fb58…5992
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x8b2b7213…4899
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
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 0x09ea36ec00…3eb8c6
Audit this contract →
← previous block·next block →recent activity