← previous blocknext block →recent activity
Analyzing
Block #101,682,512
27 transactions · 20 stateful · 2026-09-03 18:10:24 UTC
Parallelism
81/100
Blocked
55%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,682,512 · 27 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w37w19w211w012w113w214w315w325w126w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f17174f…68b4
0x34b655…2a6f
8 touches
6 conflicts
0x4736f680…60d2
0x34b655…2a6f
8 touches
6 conflicts
0x5f749304…d1c1
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0xf9bc8f1f…04f9
0x34b655…2a6f
8 touches
6 conflicts
0x64a03c12…db78
0x34b655…2a6f
6 touches
3 conflicts
0xdec2aeb2…0586
0x34b655…2a6f
6 touches
3 conflicts
0x9b4f173c…94e6
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x2f17174f4c…6568b4
Audit this contract →
← previous block·next block →recent activity