← previous blocknext block →recent activity
Analyzing
Block #106,190,676
23 transactions · 23 stateful · 2026-09-19 13:36:39 UTC
Parallelism
70/100
Blocked
52%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,190,676 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w18w010w211w212w313w114w415w516w620w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd7bbf1c1…d16d
0x34b655…2a6f
14 touches
21 conflicts
0xe22ab637…7a8e
0x34b655…2a6f
6 touches
3 conflicts
0x1d351a9b…f2dd
0x34b655…2a6f
4 touches
1 conflict
0x24ed74ea…a3ff
0x34b655…2a6f
4 touches
1 conflict
0x315e07b8…9823
0x34b655…2a6f
4 touches
1 conflict
0x92b49f44…ee4f
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
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
21 conflicts on slot 0xd7bbf1c12d…33d16d
Audit this contract →
← previous block·next block →recent activity