← previous blocknext block →recent activity
Analyzing
Block #99,866,317
21 transactions · 19 stateful · 2026-08-28 09:46:49 UTC
Parallelism
86/100
Blocked
26%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,866,317 · 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
1w02w03w14w18w010w116w017w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd22d0fc…64fd
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0xc7aa2065…2654
0x34b655…2a6f
4 touches
1 conflict
0x272e6316…bbe8
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x64a785e4…0110
0x34b655…2a6f
2 touches
0 conflicts
0x706b0bba…fd23
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 0xbd22d0fc04…0464fd
Audit this contract →
← previous block·next block →recent activity