← previous blocknext block →recent activity
Analyzing
Block #101,973,270
27 transactions · 26 stateful · 2026-09-04 18:36:18 UTC
Parallelism
70/100
Blocked
42%
Avg conflicts / tx
1.7
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #101,973,270 · 27 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w17w011w112w218w219w020w121w222w323w424w525w626w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x91b13e91…855d
0x34b655…2a6f
6 touches
3 conflicts
0xb409e204…89ac
0x34b655…2a6f
6 touches
3 conflicts
0xf1dd081e…fff1
0x34b655…2a6f
5 touches
3 conflicts
0x3967a4c9…c000
0x34b655…2a6f
4 touches
1 conflict
0x758679c1…2e12
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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity