← previous blocknext block →recent activity
Analyzing
Block #106,100,260
16 transactions · 15 stateful · 2026-09-19 06:01:37 UTC
Parallelism
63/100
Blocked
40%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,100,260 · 16 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
1w02w110w011w112w213w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x10e3c6e4…0c5c
0x6f6493…b480
12 touches
15 conflicts
0x1331697a…3ddc
0x6f6493…b480
12 touches
15 conflicts
0x13fa0fbe…8f4b
0x6f6493…b480
12 touches
15 conflicts
0x1f531dfa…9a72
0x6f6493…b480
12 touches
15 conflicts
0x30196546…4b51
0x6f6493…b480
12 touches
15 conflicts
0x45d7e324…9842
0x6f6493…b480
12 touches
15 conflicts
0x574e0a02…0fc8
0x6f6493…b480
12 touches
15 conflicts
0x5e3e1989…64cf
0x6f6493…b480
12 touches
15 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
15 conflicts on slot 0x10e3c6e42d…dd0c5c
Audit this contract →
← previous block·next block →recent activity