← previous blocknext block →recent activity
Analyzing
Block #106,452,644
38 transactions · 36 stateful · 2026-09-20 11:35:11 UTC
Parallelism
79/100
Blocked
67%
Avg conflicts / tx
1.42
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,452,644 · 38 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w09w110w215w118w220w122w224w327w328w429w530w631w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2ecffdb2…0a01
0x34b655…2a6f
12 touches
15 conflicts
0x89eaf36a…4e48
0x34b655…2a6f
12 touches
15 conflicts
0xea6f9041…e46d
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xbaf6ed88…c179
0x34b655…2a6f
8 touches
6 conflicts
0x94e7f277…471b
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
15 conflicts on slot 0x2ecffdb210…300a01
Audit this contract →
← previous block·next block →recent activity