← previous blocknext block →recent activity
Analyzing
Block #101,994,033
19 transactions · 17 stateful · 2026-09-04 20:21:43 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
1.11
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,994,033 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w26w38w49w514w015w617w518w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x4ab70ccd…2683
0x34b655…2a6f
6 touches
3 conflicts
0x25fd5528…ff50
0x34b655…2a6f
6 touches
3 conflicts
0xae8a7697…9685
0x34b655…2a6f
5 touches
3 conflicts
0x738d841d…3c29
0x34b655…2a6f
4 touches
1 conflict
0x7ac9dde0…e2ed
0x34b655…2a6f
4 touches
1 conflict
0x9a481dca…1e7a
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
15 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity