← previous blocknext block →recent activity
Analyzing
Block #101,839,236
15 transactions · 14 stateful · 2026-09-04 07:18:41 UTC
Parallelism
80/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,839,236 · 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
1w013w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b4f173c…94e6
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x02372d42…1871
0x34b655…2a6f
2 touches
0 conflicts
0x034ffefb…8e17
0x34b655…2a6f
2 touches
0 conflicts
0x15a42387…c791
0x34b655…2a6f
2 touches
0 conflicts
0x53e08444…d671
0x34b655…2a6f
2 touches
0 conflicts
0x568b9ea1…3655
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 0x9b4f173cee…8c94e6
Audit this contract →
← previous block·next block →recent activity