← previous blocknext block →recent activity
Analyzing
Block #106,471,289
32 transactions · 23 stateful · 2026-09-20 13:09:01 UTC
Parallelism
88/100
Blocked
39%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,471,289 · 32 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
1w02w03w14w05w113w015w117w218w019w121w224w227w129w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2facdba…7a7e
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xb1e4ade9…32de
0x34b655…2a6f
6 touches
3 conflicts
0x5655f5c3…6b75
0x34b655…2a6f
4 touches
1 conflict
0x67af18ee…a309
0x34b655…2a6f
4 touches
1 conflict
0x94e7f277…471b
0x34b655…2a6f
4 touches
1 conflict
0x99d66bcb…0fcb
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
3 conflicts on slot 0xd2facdbaf5…4f7a7e
Audit this contract →
← previous block·next block →recent activity