← previous blocknext block →recent activity
Analyzing
Block #105,626,590
43 transactions · 30 stateful · 2026-09-17 14:15:12 UTC
Parallelism
86/100
Blocked
40%
Avg conflicts / tx
0.51
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,626,590 · 43 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
2w03w17w08w19w210w313w015w117w019w127w429w133w034w435w536w241w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c20d376…0819
0x34b655…2a6f
8 touches
6 conflicts
0x55227071…0133
0x34b655…2a6f
6 touches
3 conflicts
0x6d955786…1327
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x361bcf51…47ef
0x34b655…2a6f
6 touches
3 conflicts
0x0747620e…9781
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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
6 conflicts on slot 0x4c20d37631…040819
Audit this contract →
← previous block·next block →recent activity