← previous blocknext block →recent activity
Analyzing
Block #106,186,873
21 transactions · 21 stateful · 2026-09-19 13:17:31 UTC
Parallelism
76/100
Blocked
48%
Avg conflicts / tx
1.14
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,186,873 · 21 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
1w02w03w14w05w16w17w210w112w014w115w216w317w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x000bde1a…e123
0x34b655…2a6f
8 touches
6 conflicts
0xc6aed34c…5ef6
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0xd4230a60…bd13
0x34b655…2a6f
8 touches
6 conflicts
0xd911522b…e960
0x34b655…2a6f
8 touches
6 conflicts
0xdf717eac…a7e8
0x34b655…2a6f
8 touches
6 conflicts
0xee64690f…0799
0x34b655…2a6f
8 touches
6 conflicts
0xfaf89f45…ced6
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
6 conflicts on slot 0x000bde1afc…91e123
Audit this contract →
← previous block·next block →recent activity