← previous blocknext block →recent activity
Analyzing
Block #101,095,411
14 transactions · 14 stateful · 2026-09-01 16:56:37 UTC
Parallelism
86/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,095,411 · 14 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
2w03w04w15w18w09w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x303f408b…b10e
0x8964d7…10f8
4 touches
1 conflict
0x303f408b…b10f
0x8964d7…10f8
4 touches
1 conflict
0x9e1a2b8b…e6ab
0x8964d7…10f8
4 touches
1 conflict
0x9e1a2b8b…e6ac
0x8964d7…10f8
4 touches
1 conflict
0x9e1a2b8b…e6ae
0x8964d7…10f8
4 touches
1 conflict
0x0476d77b…a514
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x177211e2…1c2d
0x754704…b603
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 0x303f408b5a…76b10e
Audit this contract →
← previous block·next block →recent activity