← previous blocknext block →recent activity
Analyzing
Block #101,680,886
26 transactions · 19 stateful · 2026-09-03 18:02:13 UTC
Parallelism
85/100
Blocked
47%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,680,886 · 26 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
1w03w18w19w010w111w012w118w119w220w321w022w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x2130a548…c1de
0x34b655…2a6f
6 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0xbf756c9b…2dbd
0x34b655…2a6f
6 touches
3 conflicts
0xc7ba0fe6…a860
0x34b655…2a6f
5 touches
3 conflicts
0x0b54d837…ec2c
0xd32edf…ff58
5 touches
3 conflicts
0x41469894…598f
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity