← previous blocknext block →recent activity
Analyzing
Block #102,270,767
28 transactions · 22 stateful · 2026-09-05 19:44:15 UTC
Parallelism
86/100
Blocked
23%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,270,767 · 28 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
4w05w17w014w116w217w324w027w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26507b14…ae7c
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd99d25df…ecd8
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xdfac3ce0…6699
0x99c7a7…8bf0
4 touches
1 conflict
0xc1da8f73…484c
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0x00532bf5…5711
0x754704…b603
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 0x26507b14e1…63ae7c
Audit this contract →
← previous block·next block →recent activity