← previous blocknext block →recent activity
Analyzing
Block #106,790,210
40 transactions · 35 stateful · 2026-09-21 15:55:06 UTC
Parallelism
70/100
Blocked
66%
Avg conflicts / tx
1.9
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #106,790,210 · 40 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w08w19w010w112w013w114w215w120w223w224w325w426w527w628w729w830w931w1032w1133w134w137w339w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f5d7ccd…83d4
0x34b655…2a6f
16 touches
28 conflicts
0xd4a98226…0332
0x34b655…2a6f
14 touches
21 conflicts
0x1b25f260…c429
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xabf57eb6…416d
0x34b655…2a6f
8 touches
6 conflicts
0x2c2db8e9…fdc7
0x34b655…2a6f
8 touches
6 conflicts
0x5e2ea201…12de
0x34b655…2a6f
8 touches
6 conflicts
0x4f3612e6…cb3f
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
28 conflicts on slot 0x6f5d7ccdbe…db83d4
Audit this contract →
← previous block·next block →recent activity