← previous blocknext block →recent activity
Analyzing
Block #102,480,631
22 transactions · 20 stateful · 2026-09-06 13:27:31 UTC
Parallelism
82/100
Blocked
35%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,480,631 · 22 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
1w02w03w16w07w09w010w113w114w015w117w218w320w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x58b27dde…52d1
0x34b655…2a6f
4 touches
1 conflict
0x66d0c4a4…add3
0x34b655…2a6f
4 touches
1 conflict
0x67043b0b…97d7
0x34b655…2a6f
4 touches
1 conflict
0x6b09fb8c…5518
0x34b655…2a6f
4 touches
1 conflict
0x791b78b0…2ad8
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity