← previous blocknext block →recent activity
Analyzing
Block #102,274,211
13 transactions · 11 stateful · 2026-09-05 20:01:44 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,274,211 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x045532dd…4b7d
0x34b655…2a6f
4 touches
1 conflict
0xa2eaf598…2cb0
0x34b655…2a6f
4 touches
1 conflict
0xab3df58f…531b
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x87005e20…e6f5
0x34b655…2a6f
4 touches
1 conflict
0xca544518…82c2
0x34b655…2a6f
3 touches
1 conflict
0x2891f7b7…bc9c
0x34b655…2a6f
2 touches
0 conflicts
0x2d02f869…1f83
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 0x045532dd4b…244b7d
Audit this contract →
← previous block·next block →recent activity