← previous blocknext block →recent activity
Analyzing
Block #100,869,401
17 transactions · 16 stateful · 2026-08-31 21:59:17 UTC
Parallelism
76/100
Blocked
31%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,869,401 · 17 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
1w02w15w28w09w110w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b3b66d3…8635
0x34b655…2a6f
8 touches
6 conflicts
0x5c455afd…ce06
0x34b655…2a6f
8 touches
6 conflicts
0xf692017e…686e
0x34b655…2a6f
6 touches
3 conflicts
0x1194c689…7be0
0x34b655…2a6f
6 touches
3 conflicts
0x53f7214d…8ec6
0x34b655…2a6f
6 touches
3 conflicts
0xccebf5c5…8758
0x34b655…2a6f
6 touches
3 conflicts
0xb0e4f69d…34e5
0x1b6862…e19c
4 touches
1 conflict
0xd895ee0b…d301
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 0x5b3b66d370…a88635
Audit this contract →
← previous block·next block →recent activity