← previous blocknext block →recent activity
Analyzing
Block #102,316,997
27 transactions · 23 stateful · 2026-09-05 23:38:30 UTC
Parallelism
78/100
Blocked
39%
Avg conflicts / tx
0.78
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,316,997 · 27 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
7w08w116w117w218w319w420w524w325w426w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa0a435fa…8773
0x34b655…2a6f
10 touches
10 conflicts
0xe108b282…58b3
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x83f3d320…fb59
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x6b267bdf…b173
0x34b655…2a6f
4 touches
1 conflict
0x7462b8f2…6312
0x34b655…2a6f
4 touches
1 conflict
0x7e75b2f2…e147
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
10 conflicts on slot 0xa0a435fad2…0b8773
Audit this contract →
← previous block·next block →recent activity