← previous blocknext block →recent activity
Analyzing
Block #102,532,242
16 transactions · 15 stateful · 2026-09-06 17:49:18 UTC
Parallelism
69/100
Blocked
40%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,532,242 · 16 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
1w03w14w05w29w010w112w313w414w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x766f19bb…75dd
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x11db128b…1153
0x34b655…2a6f
4 touches
1 conflict
0x2d94ecd9…43db
0x34b655…2a6f
4 touches
1 conflict
0x2dc087a5…dc53
0x34b655…2a6f
4 touches
1 conflict
0x3b5fbc7d…c8fe
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x8d4c0bb9…ccd3
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 0x766f19bbd6…c975dd
Audit this contract →
← previous block·next block →recent activity