← previous blocknext block →recent activity
Analyzing
Block #101,491,686
27 transactions · 26 stateful · 2026-09-03 02:10:25 UTC
Parallelism
85/100
Blocked
35%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,491,686 · 27 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
4w06w08w09w110w111w213w114w217w018w120w125w126w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92bb4e9d…0f03
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xfefb0189…f726
0x34b655…2a6f
4 touches
1 conflict
0x30c5329c…711c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x3817764d…242b
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5d6da397…6c5c
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 0x92bb4e9d40…fa0f03
Audit this contract →
← previous block·next block →recent activity