← previous blocknext block →recent activity
Analyzing
Block #102,039,548
29 transactions · 27 stateful · 2026-09-05 00:12:15 UTC
Parallelism
86/100
Blocked
33%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,039,548 · 29 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
1w02w14w05w17w08w09w114w015w116w117w018w122w226w227w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x045532dd…4b7d
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x1db5837f…1264
0x34b655…2a6f
4 touches
1 conflict
0x2a293f4a…3f46
0x34b655…2a6f
4 touches
1 conflict
0x53e08444…d671
0x34b655…2a6f
4 touches
1 conflict
0x67043b0b…97d7
0x34b655…2a6f
4 touches
1 conflict
0x6823c28e…594c
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0x045532dd4b…244b7d
Audit this contract →
← previous block·next block →recent activity