← previous blocknext block →recent activity
Analyzing
Block #105,919,426
22 transactions · 20 stateful · 2026-09-18 14:51:21 UTC
Parallelism
73/100
Blocked
45%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,919,426 · 22 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
2w06w08w110w211w112w313w414w515w016w117w219w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4089d428…b018
0x34b655…2a6f
10 touches
10 conflicts
0x5b6af007…0f35
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x23ee9bad…c511
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xeb4d48cc…1e26
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
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
10 conflicts on slot 0x4089d42830…afb018
Audit this contract →
← previous block·next block →recent activity