← previous blocknext block →recent activity
Analyzing
Block #105,618,729
24 transactions · 23 stateful · 2026-09-17 13:35:37 UTC
Parallelism
83/100
Blocked
43%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,618,729 · 24 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
1w02w13w04w05w16w111w213w118w119w220w221w323w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e135144…4167
0x34b655…2a6f
8 touches
6 conflicts
0x38b6ee89…0956
0x34b655…2a6f
8 touches
6 conflicts
0x6ca0994e…02ef
0x34b655…2a6f
8 touches
6 conflicts
0xcadd9a74…8bb7
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x950e74f7…2a34
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
6 conflicts on slot 0x4e135144ab…684167
Audit this contract →
← previous block·next block →recent activity