← previous blocknext block →recent activity
Analyzing
Block #101,501,057
19 transactions · 16 stateful · 2026-09-03 02:57:34 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
0.84
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,501,057 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w210w312w013w117w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb75367ff…a2b7
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0xb58ed141…c32e
0x34b655…2a6f
8 touches
6 conflicts
0x0ffac39e…6d34
0x34b655…2a6f
6 touches
3 conflicts
0x336486a4…20bd
0x34b655…2a6f
6 touches
3 conflicts
0xda50c9d5…674e
0x34b655…2a6f
6 touches
3 conflicts
0xc853be2d…b18f
0x34b655…2a6f
6 touches
3 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 0xb75367ffdb…6fa2b7
Audit this contract →
← previous block·next block →recent activity