← previous blocknext block →recent activity
Analyzing
Block #106,430,012
40 transactions · 29 stateful · 2026-09-20 09:41:12 UTC
Parallelism
88/100
Blocked
38%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,430,012 · 40 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
1w02w113w014w115w016w017w122w023w227w230w331w332w436w037w138w239w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4fb18076…caa0
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xba33378a…f1df
0x34b655…2a6f
8 touches
6 conflicts
0x8d175439…fb79
0x34b655…2a6f
6 touches
3 conflicts
0xee4fe1f7…3ead
0x34b655…2a6f
6 touches
3 conflicts
0x811fb6f4…5197
0x34b655…2a6f
6 touches
3 conflicts
0x502b3ee1…7f7c
0x34b655…2a6f
4 touches
1 conflict
0x5de6b611…5ef1
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
10 conflicts on slot 0x4fb180765d…afcaa0
Audit this contract →
← previous block·next block →recent activity