← previous blocknext block →recent activity
Analyzing
Block #101,664,310
21 transactions · 21 stateful · 2026-09-03 16:38:50 UTC
Parallelism
81/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,664,310 · 21 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
1w02w13w25w19w010w113w016w119w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb31cd67f…7a87
0x34b655…2a6f
5 touches
3 conflicts
0x29a58269…011a
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x52def5f0…2f14
0x34b655…2a6f
4 touches
1 conflict
0x5f749304…d1c1
0x34b655…2a6f
4 touches
1 conflict
0x6237161e…6c13
0x34b655…2a6f
4 touches
1 conflict
0x67c1f465…38b3
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
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 0xb31cd67f67…8f7a87
Audit this contract →
← previous block·next block →recent activity