← previous blocknext block →recent activity
Analyzing
Block #105,626,145
25 transactions · 22 stateful · 2026-09-17 14:12:57 UTC
Parallelism
84/100
Blocked
41%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,626,145 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w18w29w010w113w214w319w020w121w023w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x9e25b441…f874
0x23df56…3f97
4 touches
1 conflict
0x9e25b441…f8d5
0x23df56…3f97
4 touches
1 conflict
0xb7116dba…bb1d
0x23df56…3f97
4 touches
1 conflict
0xbdd0dc11…c953
0x23df56…3f97
4 touches
1 conflict
0xbdd0dc11…c956
0x23df56…3f97
4 touches
1 conflict
0x173d0187…365b
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity