← previous blocknext block →recent activity
Analyzing
Block #106,283,270
23 transactions · 19 stateful · 2026-09-19 21:22:45 UTC
Parallelism
78/100
Blocked
42%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,283,270 · 23 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
2w03w14w15w28w09w116w017w118w219w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ab08937…5202
0x6f6493…b480
10 touches
10 conflicts
0x0d6617e8…d567
0x6f6493…b480
10 touches
10 conflicts
0x198a462e…3a7a
0x6f6493…b480
10 touches
10 conflicts
0x1a6b911e…d130
0x6f6493…b480
10 touches
10 conflicts
0x1ef3eb39…2c67
0x6f6493…b480
10 touches
10 conflicts
0x23541fc8…19e5
0x6f6493…b480
10 touches
10 conflicts
0x297dae18…4333
0x6f6493…b480
10 touches
10 conflicts
0x2cc14fb0…e6d1
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 0x0ab08937a6…d85202
Audit this contract →
← previous block·next block →recent activity