← previous blocknext block →recent activity
Analyzing
Block #106,028,719
33 transactions · 29 stateful · 2026-09-19 00:01:36 UTC
Parallelism
85/100
Blocked
45%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,028,719 · 33 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
4w05w19w010w115w016w117w018w119w220w321w422w024w125w226w229w030w131w232w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c58f5fe…b17e
0x6f6493…b480
10 touches
10 conflicts
0x0eec5020…eb24
0x6f6493…b480
10 touches
10 conflicts
0x11e59547…b5b2
0x6f6493…b480
10 touches
10 conflicts
0x13827ab9…4945
0x6f6493…b480
10 touches
10 conflicts
0x1abff5cf…3221
0x6f6493…b480
10 touches
10 conflicts
0x228def3f…7265
0x6f6493…b480
10 touches
10 conflicts
0x237b1762…9c0e
0x6f6493…b480
10 touches
10 conflicts
0x2813d1fb…bb9f
0x6f6493…b480
10 touches
10 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: 0x6f6493e3…08b480
10 conflicts on slot 0x0c58f5fe53…17b17e
Audit this contract →
← previous block·next block →recent activity