← previous blocknext block →recent activity
Analyzing
Block #105,620,259
23 transactions · 23 stateful · 2026-09-17 13:43:19 UTC
Parallelism
65/100
Blocked
43%
Avg conflicts / tx
1.35
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,620,259 · 23 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
1w02w03w14w25w36w47w58w69w713w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x033ec72e…2949
0x34b655…2a6f
16 touches
28 conflicts
0xd33c2ab5…ccc3
0x34b655…2a6f
14 touches
21 conflicts
0xcd5c0ecb…4b5f
0x34b655…2a6f
10 touches
10 conflicts
0x6c0e32fc…a6ca
0x34b655…2a6f
10 touches
10 conflicts
0xd5398303…808b
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x6237b89c…9779
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot 0x033ec72ebf…a12949
Audit this contract →
← previous block·next block →recent activity