← previous blocknext block →recent activity
Analyzing
Block #105,930,096
15 transactions · 13 stateful · 2026-09-18 15:45:04 UTC
Parallelism
67/100
Blocked
54%
Avg conflicts / tx
0.93
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,930,096 · 15 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
1w02w03w14w15w17w29w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xd2facdba…7a7e
0x34b655…2a6f
8 touches
6 conflicts
0x80d639be…fd4a
0x34b655…2a6f
6 touches
3 conflicts
0x581b829b…9578
0x34b655…2a6f
4 touches
1 conflict
0x5ff01ee9…5a45
0x34b655…2a6f
4 touches
1 conflict
0xed96bd10…898c
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x17bb579f…938c
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 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity