← previous blocknext block →recent activity
Analyzing
Block #99,871,357
14 transactions · 14 stateful · 2026-08-28 10:12:11 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,871,357 · 14 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
2w03w15w06w07w18w09w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x359866c7…de7b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0xbad4e90b…33a5
0x34b655…2a6f
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x8a3051ef…ade2
0xe52b14…7230
3 touches
1 conflict
0x8a4c4436…e748
0x34b655…2a6f
2 touches
0 conflicts
0xabdf81c9…b3b0
0x34b655…2a6f
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
3 conflicts on slot 0x359866c739…efde7b
Audit this contract →
← previous block·next block →recent activity