← previous blocknext block →recent activity
Analyzing
Block #103,211,356
20 transactions · 19 stateful · 2026-09-09 02:55:20 UTC
Parallelism
85/100
Blocked
26%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #103,211,356 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w013w014w116w218w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4e19ae4…0788
0xe7cd86…c82d
4 touches
1 conflict
0xb2d0be3b…080d
0x065c9d…c394
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x65e795ca…0320
0x34b655…2a6f
4 touches
1 conflict
0x7684f61e…fc67
0x34b655…2a6f
4 touches
1 conflict
0xa418f585…39b0
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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: 0xe7cd86e1…0fc82d
1 conflict on slot 0xc4e19ae47e…dc0788
Audit this contract →
← previous block·next block →recent activity