← previous blocknext block →recent activity
Analyzing
Block #102,745,368
23 transactions · 20 stateful · 2026-09-07 11:45:05 UTC
Parallelism
70/100
Blocked
45%
Avg conflicts / tx
1.13
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,745,368 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w09w110w211w312w413w514w616w017w018w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaf5fe80…1ffc
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xf0dd0b1d…6cd8
0x34b655…2a6f
6 touches
3 conflicts
0x948836ff…59ab
0x34b655…2a6f
5 touches
3 conflicts
0x0f43bfc7…1de5
0x34b655…2a6f
5 touches
3 conflicts
0x9cf9008a…d826
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
21 conflicts on slot 0xfaf5fe80ab…a71ffc
Audit this contract →
← previous block·next block →recent activity