← previous blocknext block →recent activity
Analyzing
Block #103,040,033
22 transactions · 22 stateful · 2026-09-08 12:31:35 UTC
Parallelism
82/100
Blocked
23%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #103,040,033 · 22 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
2w03w14w05w112w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x382434ca…96b5
0x34b655…2a6f
8 touches
6 conflicts
0x9aed5849…2f7e
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xee8237bd…46ad
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x413476a1…3e03
0x851145…3f07
4 touches
1 conflict
0xbb8dd99f…bb3f
0x851145…3f07
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
6 conflicts on slot 0x382434ca57…4d96b5
Audit this contract →
← previous block·next block →recent activity