← previous blocknext block →recent activity
Analyzing
Block #101,799,898
15 transactions · 15 stateful · 2026-09-04 04:00:49 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,799,898 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w012w013w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7a6cb97…66f1
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x731d7308…fd26
0x34b655…2a6f
4 touches
1 conflict
0x85eb1316…bb9e
0x34b655…2a6f
4 touches
1 conflict
0xc6615a36…3cf0
0x34b655…2a6f
4 touches
1 conflict
0x30f7b5bf…14c6
0x34b655…2a6f
2 touches
0 conflicts
0x3fb3f2e2…fef3
0x34b655…2a6f
2 touches
0 conflicts
0x51d0a65c…5e21
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
3 conflicts on slot 0xc7a6cb976a…5966f1
Audit this contract →
← previous block·next block →recent activity