← previous blocknext block →recent activity
Analyzing
Block #102,279,941
13 transactions · 12 stateful · 2026-09-05 20:30:49 UTC
Parallelism
69/100
Blocked
42%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,279,941 · 13 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
1w02w13w25w09w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2038f2e6…73b1
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xf4077a52…07e1
0x34b655…2a6f
6 touches
3 conflicts
0x20b94f7c…2a9b
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x8590b692…b267
0x34b655…2a6f
6 touches
3 conflicts
0xd5b10148…e631
0x1b6862…e19c
4 touches
1 conflict
0xd7908b5f…56b9
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
6 conflicts on slot 0x2038f2e684…e573b1
Audit this contract →
← previous block·next block →recent activity