← previous blocknext block →recent activity
Analyzing
Block #106,038,413
21 transactions · 18 stateful · 2026-09-19 00:50:23 UTC
Parallelism
71/100
Blocked
28%
Avg conflicts / tx
0.43
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,038,413 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w217w318w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x48828733…fd48
0x34b655…2a6f
8 touches
6 conflicts
0xbc8fb280…76a3
0x34b655…2a6f
8 touches
6 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
8 touches
6 conflicts
0x309f47c0…e1cf
0x34b655…2a6f
6 touches
3 conflicts
0x3b65c5ca…9f83
0x34b655…2a6f
6 touches
3 conflicts
0x48b6f2c7…2ef7
0x34b655…2a6f
6 touches
3 conflicts
0x5ad5e6de…e7ad
0x34b655…2a6f
6 touches
3 conflicts
0x6d5d1fb5…86a7
0x34b655…2a6f
6 touches
3 conflicts
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 0x488287332c…96fd48
Audit this contract →
← previous block·next block →recent activity