← previous blocknext block →recent activity
Analyzing
Block #103,222,356
19 transactions · 17 stateful · 2026-09-09 03:50:45 UTC
Parallelism
89/100
Blocked
24%
Avg conflicts / tx
0.26
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #103,222,356 · 19 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
1w06w19w010w111w012w014w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x045532dd…4b7d
0x34b655…2a6f
4 touches
1 conflict
0x0f13b598…f75b
0x34b655…2a6f
4 touches
1 conflict
0x0fb116d3…6486
0x34b655…2a6f
4 touches
1 conflict
0x98b14f9b…08b3
0x34b655…2a6f
4 touches
1 conflict
0xe6d9c62e…465a
0x34b655…2a6f
4 touches
1 conflict
0xfa09be5a…1e79
0x34b655…2a6f
4 touches
1 conflict
0xfcd5e68f…2a12
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
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 0x045532dd4b…244b7d
Audit this contract →
← previous block·next block →recent activity