← previous blocknext block →recent activity
Analyzing
Block #106,242,256
16 transactions · 16 stateful · 2026-09-19 17:56:21 UTC
Parallelism
69/100
Blocked
25%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,242,256 · 16 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
2w03w14w25w311w012w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x98568c43…ff4e
0x34b655…2a6f
10 touches
10 conflicts
0x6c804088…250d
0x34b655…2a6f
8 touches
6 conflicts
0x159cff26…7665
0x34b655…2a6f
6 touches
3 conflicts
0xdf64e5e6…75e8
0x34b655…2a6f
6 touches
3 conflicts
0xfcdd1e1e…577e
0x34b655…2a6f
4 touches
1 conflict
0x1b25f260…c429
0x34b655…2a6f
4 touches
1 conflict
0x1c8da57f…263a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0x98568c43d7…70ff4e
Audit this contract →
← previous block·next block →recent activity