← previous blocknext block →recent activity
Analyzing
Block #105,403,508
28 transactions · 23 stateful · 2026-09-16 19:32:25 UTC
Parallelism
79/100
Blocked
43%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,403,508 · 28 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w08w19w217w219w320w421w527w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0x05b82e92…351d
0x34b655…2a6f
10 touches
10 conflicts
0xad1ecaad…f0d1
0x34b655…2a6f
10 touches
10 conflicts
0x6771eae2…7014
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x227b62da…8563
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x96e4bcd4…28b8
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity