← previous blocknext block →recent activity
Analyzing
Block #101,989,516
22 transactions · 15 stateful · 2026-09-04 19:58:46 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.27
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,989,516 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w113w015w116w219w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x25c0f8b5…4246
0x754704…b603
4 touches
1 conflict
0x8226c92c…ece7
0x754704…b603
4 touches
1 conflict
0xe4940a46…26a0
0x754704…b603
4 touches
1 conflict
0x3b9910a2…6177
0x99c7a7…8bf0
4 touches
1 conflict
0xd6d0e119…6a6a
0x99c7a7…8bf0
4 touches
1 conflict
0x2c84cfcc…351b
0x34b655…2a6f
4 touches
1 conflict
0x58620f29…db5a
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 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity