← previous blocknext block →recent activity
Analyzing
Block #106,467,632
16 transactions · 12 stateful · 2026-09-20 12:50:36 UTC
Parallelism
88/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,467,632 · 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
1w03w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe3abe489…ebf3
0x4de0d8…bfc3
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x0fd2cbc5…476b
0x4de0d8…bfc3
4 touches
1 conflict
0xa2835318…eb27
0x4de0d8…bfc3
4 touches
1 conflict
0x0ed7cc0b…ee52
0x34b655…2a6f
2 touches
0 conflicts
0x3b0745b1…5e0c
0x34b655…2a6f
2 touches
0 conflicts
0x4265984a…a7d2
0x34b655…2a6f
2 touches
0 conflicts
0x519ff17c…69c2
0x34b655…2a6f
2 touches
0 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: 0x4de0d89d…36bfc3
1 conflict on slot 0xe3abe4895e…e5ebf3
Audit this contract →
← previous block·next block →recent activity