← previous blocknext block →recent activity
Analyzing
Block #103,210,982
19 transactions · 18 stateful · 2026-09-09 02:53:27 UTC
Parallelism
79/100
Blocked
44%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #103,210,982 · 19 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
1w02w03w15w06w17w212w113w214w315w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab042dd2…5f5f
0x34b655…2a6f
6 touches
3 conflicts
0x4f3d1bb8…76b3
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xe6b16d23…9ee9
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x2bb0d58d…9dcf
0x34b655…2a6f
4 touches
1 conflict
0x4b84a880…6abb
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 0xab042dd2e5…955f5f
Audit this contract →
← previous block·next block →recent activity