← previous blocknext block →recent activity
Analyzing
Block #101,989,080
25 transactions · 21 stateful · 2026-09-04 19:56:33 UTC
Parallelism
88/100
Blocked
38%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,989,080 · 25 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
1w02w13w25w08w111w012w113w014w121w123w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee109478…a9c1
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x0d38d7bb…1dd3
0x34b655…2a6f
4 touches
1 conflict
0x23b0f222…aa59
0x34b655…2a6f
4 touches
1 conflict
0x3e7ad612…e804
0x34b655…2a6f
4 touches
1 conflict
0x492dfcee…984c
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0x67c1f465…38b3
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 0xee109478ee…ffa9c1
Audit this contract →
← previous block·next block →recent activity