← previous blocknext block →recent activity
Analyzing
Block #103,215,931
15 transactions · 14 stateful · 2026-09-09 03:18:22 UTC
Parallelism
87/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #103,215,931 · 15 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
2w03w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x89532525…6dbf
0xe52b14…7230
3 touches
1 conflict
0x0ff8ead2…e970
0x34b655…2a6f
2 touches
0 conflicts
0x224c42ff…7e8a
0x34b655…2a6f
2 touches
0 conflicts
0x24c1343e…9e0c
0x34b655…2a6f
2 touches
0 conflicts
0x524f0872…0d12
0x34b655…2a6f
2 touches
0 conflicts
0x55192654…91fe
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 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity