← previous blocknext block →recent activity
Analyzing
Block #103,216,027
13 transactions · 11 stateful · 2026-09-09 03:18:51 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #103,216,027 · 13 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
3w04w17w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x754bbcbe…427e
0x34b655…2a6f
6 touches
3 conflicts
0x58620f29…db5a
0x34b655…2a6f
4 touches
1 conflict
0x5ee1769f…2d59
0x34b655…2a6f
4 touches
1 conflict
0x73d6a7f4…962b
0x34b655…2a6f
4 touches
1 conflict
0x747f609d…1555
0x34b655…2a6f
4 touches
1 conflict
0x9421a154…d296
0x34b655…2a6f
4 touches
1 conflict
0xb1afd450…7919
0x34b655…2a6f
4 touches
1 conflict
0xc51d0574…a2bc
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 0x754bbcbe52…67427e
Audit this contract →
← previous block·next block →recent activity