← previous blocknext block →recent activity
Analyzing
Block #101,972,084
14 transactions · 13 stateful · 2026-09-04 18:30:16 UTC
Parallelism
86/100
Blocked
23%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,972,084 · 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
4w05w16w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeee854e5…e77b
0x34b655…2a6f
4 touches
1 conflict
0x7e06d07b…36af
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xddd20e39…d524
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
2 touches
0 conflicts
0x557eab50…f26a
0x34b655…2a6f
2 touches
0 conflicts
0x56e0d685…c960
0x34b655…2a6f
2 touches
0 conflicts
0x67043b0b…97d7
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: Perpl
1 conflict on slot 0xeee854e571…73e77b
Audit this contract →
← previous block·next block →recent activity