← previous blocknext block →recent activity
Analyzing
Block #103,211,172
15 transactions · 14 stateful · 2026-09-09 02:54:25 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #103,211,172 · 15 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
1w02w13w19w012w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdecb9ef3…51c5
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdc7b9eda…e616
0x34b655…2a6f
4 touches
1 conflict
0x0d05c2b3…bd7e
0x34b655…2a6f
4 touches
1 conflict
0x0d05c2b3…bd7f
0x34b655…2a6f
4 touches
1 conflict
0x0fb116d3…6486
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 0xdecb9ef317…6151c5
Audit this contract →
← previous block·next block →recent activity