← previous blocknext block →recent activity
Analyzing
Block #106,373,421
19 transactions · 19 stateful · 2026-09-20 04:56:25 UTC
Parallelism
79/100
Blocked
32%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,373,421 · 19 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
1w02w13w24w37w312w013w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52723002…65de
0x34b655…2a6f
6 touches
3 conflicts
0x0262e1c6…52e1
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe32e848a…851e
0x34b655…2a6f
4 touches
1 conflict
0xecd87a39…d9c5
0x34b655…2a6f
4 touches
1 conflict
0x364036f4…10de
0x34b655…2a6f
4 touches
1 conflict
0x5b17b0ae…fccf
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 0x527230023f…ef65de
Audit this contract →
← previous block·next block →recent activity