← previous blocknext block →recent activity
Analyzing
Block #102,010,207
13 transactions · 12 stateful · 2026-09-04 21:43:43 UTC
Parallelism
62/100
Blocked
42%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,010,207 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w08w110w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xa5f284b7…3320
0x34b655…2a6f
6 touches
3 conflicts
0xf96d61f8…8fd8
0x754704…b603
4 touches
1 conflict
0x1d9867ad…6d9a
0x34b655…2a6f
4 touches
1 conflict
0x14636d9e…78ad
0x99c7a7…8bf0
4 touches
1 conflict
0x2a46edb5…b5bd
0x99c7a7…8bf0
4 touches
1 conflict
0x25ec781a…dca9
0x34b655…2a6f
4 touches
1 conflict
0x65ff54af…aa01
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity