← previous blocknext block →recent activity
Analyzing
Block #101,797,709
10 transactions · 9 stateful · 2026-09-04 03:49:48 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,797,709 · 10 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
1w02w16w08w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x8cba86cd…5267
0x34b655…2a6f
3 touches
1 conflict
0x2e7d54bc…8084
0x34b655…2a6f
2 touches
0 conflicts
0x3a37099d…c4d3
0x34b655…2a6f
2 touches
0 conflicts
0x3cb45e6c…97c0
0x34b655…2a6f
2 touches
0 conflicts
0x3e4fbaee…0c5f
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 0x6d1b72eefe…416b78
Audit this contract →
← previous block·next block →recent activity