← previous blocknext block →recent activity
Analyzing
Block #106,372,795
16 transactions · 15 stateful · 2026-09-20 04:53:16 UTC
Parallelism
69/100
Blocked
40%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,372,795 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w16w27w38w09w310w111w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1a655b8…21c2
0x34b655…2a6f
10 touches
10 conflicts
0x7462b8f2…6312
0x34b655…2a6f
6 touches
3 conflicts
0x70986451…c6bd
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x1e665745…8517
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
0x6183ee9a…21b1
0x34b655…2a6f
4 touches
1 conflict
0xfdfa9d6f…3824
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
10 conflicts on slot 0xb1a655b83b…bf21c2
Audit this contract →
← previous block·next block →recent activity