← previous blocknext block →recent activity
Analyzing
Block #101,096,498
36 transactions · 26 stateful · 2026-09-01 17:02:05 UTC
Parallelism
89/100
Blocked
38%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,096,498 · 36 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w28w09w112w013w114w226w027w129w130w231w335w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdcebb2b8…5f18
0x34b655…2a6f
6 touches
3 conflicts
0x4b53c962…f39c
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x58c3dacf…cb15
0x34b655…2a6f
4 touches
1 conflict
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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 0xdcebb2b809…7d5f18
Audit this contract →
← previous block·next block →recent activity