← previous blocknext block →recent activity
Analyzing
Block #105,748,724
28 transactions · 24 stateful · 2026-09-18 00:29:55 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.64
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,748,724 · 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
2w03w04w15w09w117w219w120w221w325w326w427w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x581f7011…eb5b
0x34b655…2a6f
6 touches
3 conflicts
0x3accf018…2e8b
0x34b655…2a6f
6 touches
3 conflicts
0x43e3decb…be40
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0c63d442…6d6b
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x92f8fe7e…0cf3
0x34b655…2a6f
4 touches
1 conflict
0xac27d4e9…fffc
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 0x581f701126…13eb5b
Audit this contract →
← previous block·next block →recent activity