← previous blocknext block →recent activity
Analyzing
Block #101,992,487
16 transactions · 16 stateful · 2026-09-04 20:13:52 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,992,487 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w16w07w18w29w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x55fc72dc…f3c5
0x34b655…2a6f
4 touches
1 conflict
0x74b835e1…b1bd
0x34b655…2a6f
4 touches
1 conflict
0xb5bf6c79…b71a
0x34b655…2a6f
4 touches
1 conflict
0xe1dd82aa…0e09
0x34b655…2a6f
4 touches
1 conflict
0xee46716c…d788
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: 0xf5b5f7f8…a36d70
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity