← previous blocknext block →recent activity
Analyzing
Block #105,617,159
28 transactions · 25 stateful · 2026-09-17 13:27:42 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,617,159 · 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
1w02w03w14w25w36w47w18w219w521w023w126w027w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb5b61a2…b2bc
0x34b655…2a6f
12 touches
15 conflicts
0xf15ddcaf…3106
0x34b655…2a6f
10 touches
10 conflicts
0xb0608dfe…083d
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0x1584e21a…6642
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x27d3333e…7d38
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
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
15 conflicts on slot 0xeb5b61a29c…4fb2bc
Audit this contract →
← previous block·next block →recent activity