← previous blocknext block →recent activity
Analyzing
Block #103,223,557
16 transactions · 15 stateful · 2026-09-09 03:56:47 UTC
Parallelism
88/100
Blocked
20%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #103,223,557 · 16 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
2w03w14w07w08w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0234ba60…992d
0x34b655…2a6f
4 touches
1 conflict
0x0f763490…ff64
0x34b655…2a6f
4 touches
1 conflict
0x16d79cd9…2a9c
0x34b655…2a6f
4 touches
1 conflict
0x36aa792c…a68d
0x34b655…2a6f
4 touches
1 conflict
0x3a02129f…9eaf
0x34b655…2a6f
4 touches
1 conflict
0x448fdf2a…fab4
0x34b655…2a6f
4 touches
1 conflict
0x4a76df63…319e
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 0x0234ba6036…f2992d
Audit this contract →
← previous block·next block →recent activity