← previous blocknext block →recent activity
Analyzing
Block #106,945,516
20 transactions · 20 stateful · 2026-09-22 04:56:50 UTC
Parallelism
80/100
Blocked
40%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,945,516 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w06w17w09w010w111w012w113w214w116w117w118w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d5fc820…1750
0x34b655…2a6f
8 touches
6 conflicts
0x971696fe…e1dd
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x4ee280b4…57b8
0x34b655…2a6f
4 touches
1 conflict
0x574628e9…dcc3
0x34b655…2a6f
4 touches
1 conflict
0x5f469d39…06f3
0x34b655…2a6f
4 touches
1 conflict
0x5f72d58f…c445
0x34b655…2a6f
4 touches
1 conflict
0x66b19827…9edc
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
6 conflicts on slot 0x8d5fc820e4…ea1750
Audit this contract →
← previous block·next block →recent activity