← previous blocknext block →recent activity
Analyzing
Block #102,393,824
10 transactions · 10 stateful · 2026-09-06 06:07:42 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,393,824 · 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
1w05w07w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53c41998…7d52
0x34b655…2a6f
4 touches
1 conflict
0x3b25d07f…1dee
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x01315072…0e2d
0x34b655…2a6f
2 touches
0 conflicts
0x03494e5f…4f7f
0x34b655…2a6f
2 touches
0 conflicts
0x08a1864f…aa26
0x34b655…2a6f
2 touches
0 conflicts
0x167294f0…a80b
0x34b655…2a6f
2 touches
0 conflicts
0x1d92b29d…e9da
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 0x53c41998b8…357d52
Audit this contract →
← previous block·next block →recent activity