← previous blocknext block →recent activity
Analyzing
Block #102,243,622
26 transactions · 26 stateful · 2026-09-05 17:26:43 UTC
Parallelism
85/100
Blocked
35%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,243,622 · 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
1w04w05w16w211w014w015w116w219w120w221w324w225w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe0da07e4…ccf2
0x34b655…2a6f
6 touches
3 conflicts
0xfa805f95…72a4
0x34b655…2a6f
6 touches
3 conflicts
0xfcd7574f…a3a2
0x34b655…2a6f
6 touches
3 conflicts
0x32e1d03e…68a7
0x34b655…2a6f
6 touches
3 conflicts
0x3a02129f…9eaf
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity