← previous blocknext block →recent activity
Analyzing
Block #106,537,417
43 transactions · 37 stateful · 2026-09-20 18:41:50 UTC
Parallelism
84/100
Blocked
57%
Avg conflicts / tx
1.19
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,537,417 · 43 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
1w02w15w06w17w18w215w220w223w224w326w334w435w536w537w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x79b2e66a…64e7
0x34b655…2a6f
10 touches
10 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
8 touches
6 conflicts
0x172b0de5…980b
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x2043808e…8861
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x69411fb3…e36d
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0x79b2e66a6c…4364e7
Audit this contract →
← previous block·next block →recent activity