← previous blocknext block →recent activity
Analyzing
Block #103,213,376
21 transactions · 19 stateful · 2026-09-09 03:05:30 UTC
Parallelism
76/100
Blocked
37%
Avg conflicts / tx
0.43
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #103,213,376 · 21 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
1w04w16w28w39w010w112w213w014w118w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0fb116d3…6486
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x18cf84a6…09e4
0x34b655…2a6f
4 touches
1 conflict
0x2c45dc1d…9eca
0x34b655…2a6f
4 touches
1 conflict
0x4b84a880…6abb
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
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 0x0fb116d323…216486
Audit this contract →
← previous block·next block →recent activity