← previous blocknext block →recent activity
Analyzing
Block #101,681,979
23 transactions · 17 stateful · 2026-09-03 18:07:43 UTC
Parallelism
83/100
Blocked
47%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,681,979 · 23 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
6w07w08w19w110w211w312w013w115w020w121w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xdec2aeb2…0586
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x024b482b…16b0
0x34b655…2a6f
4 touches
1 conflict
0x21a4d924…f40c
0x34b655…2a6f
4 touches
1 conflict
0x2f17174f…68b4
0x34b655…2a6f
4 touches
1 conflict
0x3fb3f2e2…fef3
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity