← previous blocknext block →recent activity
Analyzing
Block #104,868,624
6 transactions · 6 stateful · 2026-09-14 22:40:22 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #104,868,624 · 6 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
1w02w14w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xf30cdba3…6083
0x34b655…2a6f
4 touches
1 conflict
0x0d39a154…6eb5
0x34b655…2a6f
2 touches
0 conflicts
0x22c954eb…9a9e
0x34b655…2a6f
2 touches
0 conflicts
0x25180879…8191
0x34b655…2a6f
2 touches
0 conflicts
0x2cb61687…a205
0x34b655…2a6f
2 touches
0 conflicts
0x3d1a888b…ba9d
0x34b655…2a6f
2 touches
0 conflicts
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity