← previous blocknext block →recent activity
Analyzing
Block #103,215,897
18 transactions · 17 stateful · 2026-09-09 03:18:12 UTC
Parallelism
89/100
Blocked
29%
Avg conflicts / tx
0.28
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #103,215,897 · 18 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w06w17w09w010w113w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x29bc79ed…2229
0x34b655…2a6f
4 touches
1 conflict
0x2f17174f…68b4
0x34b655…2a6f
4 touches
1 conflict
0x3027f5b0…7a3f
0x34b655…2a6f
4 touches
1 conflict
0x3a02129f…9eaf
0x34b655…2a6f
4 touches
1 conflict
0x3e7ad612…e804
0x34b655…2a6f
4 touches
1 conflict
0x448fdf2a…fab4
0x34b655…2a6f
4 touches
1 conflict
0x4f526c44…ba6f
0x34b655…2a6f
4 touches
1 conflict
0x59095657…4424
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
1 conflict on slot 0x29bc79edb8…c42229
Audit this contract →
← previous block·next block →recent activity