← previous blocknext block →recent activity
Analyzing
Block #102,527,383
24 transactions · 22 stateful · 2026-09-06 17:24:41 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
1.58
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,527,383 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w27w38w410w511w616w719w521w122w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x4542f274…9d48
0x34b655…2a6f
4 touches
1 conflict
0x4b69eb87…0657
0x34b655…2a6f
4 touches
1 conflict
0x589605bf…7f62
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x834128b8…1616
0x34b655…2a6f
4 touches
1 conflict
0x9ee824ec…5faa
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
28 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity