← previous blocknext block →recent activity
Analyzing
Block #101,988,784
17 transactions · 17 stateful · 2026-09-04 19:55:04 UTC
Parallelism
71/100
Blocked
41%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,988,784 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w05w26w38w215w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6823c28e…594c
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0x02372d42…1871
0x34b655…2a6f
6 touches
3 conflicts
0xa90eb29b…2cec
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x53e08444…d671
0x34b655…2a6f
6 touches
3 conflicts
0xf7772b49…fc12
0x34b655…2a6f
6 touches
3 conflicts
0x33761f7c…8f85
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: Perpl
3 conflicts on slot 0x6823c28eb2…d0594c
Audit this contract →
← previous block·next block →recent activity