← previous blocknext block →recent activity
Analyzing
Block #105,922,134
13 transactions · 13 stateful · 2026-09-18 15:04:59 UTC
Parallelism
85/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #105,922,134 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w16w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x24c5620c…7ac5
0x34b655…2a6f
2 touches
0 conflicts
0x2c1564ce…7fa8
0x34b655…2a6f
2 touches
0 conflicts
0x3604ef61…f25d
0x34b655…2a6f
2 touches
0 conflicts
0x3d6c26e5…1b45
0x34b655…2a6f
2 touches
0 conflicts
0x4c0247e1…a87b
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity