← previous blocknext block →recent activity
Analyzing
Block #103,210,411
10 transactions · 10 stateful · 2026-09-09 02:50:34 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #103,210,411 · 10 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x045532dd…4b7d
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x6677baa1…b6c5
0x34b655…2a6f
4 touches
1 conflict
0xeb206652…6a16
0x34b655…2a6f
4 touches
1 conflict
0x13e03bf3…6a60
0x34b655…2a6f
2 touches
0 conflicts
0x18a884d4…846c
0x34b655…2a6f
2 touches
0 conflicts
0x22b4a41c…e29f
0x34b655…2a6f
2 touches
0 conflicts
0x29a58269…011a
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 0x045532dd4b…244b7d
Audit this contract →
← previous block·next block →recent activity