← previous blocknext block →recent activity
Analyzing
Block #101,839,501
13 transactions · 13 stateful · 2026-09-04 07:20:01 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.77
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,839,501 · 13 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
1w02w03w04w05w16w07w19w210w312w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x8dca7cdd…b418
0x928dc8…8207
4 touches
1 conflict
0x4ee0b65a…6d40
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xcb69a552…4424
0x34b655…2a6f
4 touches
1 conflict
0xde61be10…fd55
0x34b655…2a6f
4 touches
1 conflict
0x613560f2…8d9e
0x928dc8…8207
4 touches
1 conflict
0x6ede85f4…0b8a
0x928dc8…8207
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity