← previous blocknext block →recent activity
Analyzing
Block #103,215,242
22 transactions · 21 stateful · 2026-09-09 03:14:54 UTC
Parallelism
73/100
Blocked
43%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #103,215,242 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w310w011w112w415w016w118w219w020w221w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
10 touches
10 conflicts
0x2905ed39…1865
0x34b655…2a6f
8 touches
6 conflicts
0x0e216931…58c3
0x34b655…2a6f
8 touches
6 conflicts
0x18e881c5…b740
0x34b655…2a6f
6 touches
3 conflicts
0x22b4a41c…e29f
0x34b655…2a6f
6 touches
3 conflicts
0x2f17174f…68b4
0x34b655…2a6f
6 touches
3 conflicts
0x3e7ad612…e804
0x34b655…2a6f
6 touches
3 conflicts
0x5202469c…bec0
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity