← previous blocknext block →recent activity
Analyzing
Block #99,208,816
21 transactions · 20 stateful · 2026-08-26 02:23:55 UTC
Parallelism
81/100
Blocked
45%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,208,816 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w26w18w010w111w214w116w317w320w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c29ecd5…58b6
0x34b655…2a6f
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
0x9210e826…1414
0x34b655…2a6f
4 touches
1 conflict
0xab2b11cd…7e41
0x34b655…2a6f
4 touches
1 conflict
0xb0f5d668…99ac
0x34b655…2a6f
4 touches
1 conflict
0xbd590df7…9891
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
6 conflicts on slot 0x4c29ecd55a…1058b6
Audit this contract →
← previous block·next block →recent activity