← previous blocknext block →recent activity
Analyzing
Block #102,484,137
24 transactions · 21 stateful · 2026-09-06 13:45:16 UTC
Parallelism
83/100
Blocked
24%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,484,137 · 24 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
4w05w17w09w018w120w221w222w023w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65ff54af…aa01
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x22f10271…841d
0x34b655…2a6f
4 touches
1 conflict
0x4279d034…a3f2
0x34b655…2a6f
4 touches
1 conflict
0x4387ba94…e195
0x34b655…2a6f
4 touches
1 conflict
0x6266e26a…96ee
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
3 conflicts on slot 0x65ff54af45…13aa01
Audit this contract →
← previous block·next block →recent activity