← previous blocknext block →recent activity
Analyzing
Block #102,569,138
14 transactions · 14 stateful · 2026-09-06 20:56:28 UTC
Parallelism
71/100
Blocked
21%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,569,138 · 14 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
1w09w110w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd53cdf54…2bdd
0x34b655…2a6f
6 touches
3 conflicts
0x4ac4a2c2…2707
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbbc4bdf7…c62f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x189f735c…64fc
0x34b655…2a6f
4 touches
1 conflict
0x2e179963…86f3
0x34b655…2a6f
2 touches
0 conflicts
0x3c67d31e…3dbe
0x34b655…2a6f
2 touches
0 conflicts
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 0xd53cdf54e0…612bdd
Audit this contract →
← previous block·next block →recent activity