← previous blocknext block →recent activity
Analyzing
Block #102,267,132
19 transactions · 19 stateful · 2026-09-05 19:25:49 UTC
Parallelism
63/100
Blocked
37%
Avg conflicts / tx
0.84
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,267,132 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w011w312w413w515w617w018w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67043b0b…97d7
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x2e957c13…4777
0x34b655…2a6f
6 touches
3 conflicts
0x4113c42b…5765
0x34b655…2a6f
6 touches
3 conflicts
0x53e08444…d671
0x34b655…2a6f
6 touches
3 conflicts
0x56e0d685…c960
0x34b655…2a6f
6 touches
3 conflicts
0x5f749304…d1c1
0x34b655…2a6f
6 touches
3 conflicts
0x65f011a5…bc6e
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x67043b0b65…8297d7
Audit this contract →
← previous block·next block →recent activity