← previous blocknext block →recent activity
Analyzing
Block #106,016,902
16 transactions · 16 stateful · 2026-09-18 23:02:08 UTC
Parallelism
88/100
Blocked
25%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,016,902 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w06w17w08w111w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2d9f3c3…055b
0x928dc8…8207
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x613560f2…8d9e
0x928dc8…8207
4 touches
1 conflict
0x6ede85f4…0b8a
0x928dc8…8207
4 touches
1 conflict
0x6ede85f4…0b8b
0x928dc8…8207
4 touches
1 conflict
0x8dca7cdd…b416
0x928dc8…8207
4 touches
1 conflict
0x8dca7cdd…b418
0x928dc8…8207
4 touches
1 conflict
0x206f4379…e08a
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: 0x928dc8af…fd8207
1 conflict on slot 0xe2d9f3c30e…c1055b
Audit this contract →
← previous block·next block →recent activity