← previous blocknext block →recent activity
Analyzing
Block #101,971,844
23 transactions · 20 stateful · 2026-09-04 18:29:03 UTC
Parallelism
78/100
Blocked
20%
Avg conflicts / tx
0.35
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,971,844 · 23 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
6w09w010w119w221w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xddd20e39…d524
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe75ca10f…d28a
0x3bd359…433a
2 touches
0 conflicts
0x95e37fef…f5bf
0x3ec731…7777
2 touches
0 conflicts
0xe1158e10…ca2e
0x3ec731…7777
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
6 conflicts on slot 0xddd20e3989…a2d524
Audit this contract →
← previous block·next block →recent activity