← previous blocknext block →recent activity
Analyzing
Block #101,680,416
11 transactions · 11 stateful · 2026-09-03 17:59:51 UTC
Parallelism
82/100
Blocked
27%
Avg conflicts / tx
0.45
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,680,416 · 11 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
1w03w04w16w07w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8c0942f4…ec81
0x8964d7…10f8
4 touches
1 conflict
0x0b401393…6032
0x8964d7…10f8
4 touches
1 conflict
0x0b401393…6033
0x8964d7…10f8
4 touches
1 conflict
0x8c0942f4…ec7e
0x8964d7…10f8
4 touches
1 conflict
0x8c0942f4…ec7f
0x8964d7…10f8
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x51af0e92…4020
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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: 0x8964d7c9…5b10f8
1 conflict on slot 0x8c0942f42d…16ec81
Audit this contract →
← previous block·next block →recent activity