← previous blocknext block →recent activity
Analyzing
Block #102,020,070
12 transactions · 11 stateful · 2026-09-04 22:33:37 UTC
Parallelism
83/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,020,070 · 12 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x74b835e1…b1bd
0x34b655…2a6f
4 touches
1 conflict
0xac27d4e9…fffc
0x34b655…2a6f
4 touches
1 conflict
0xb5bf6c79…b71a
0x34b655…2a6f
4 touches
1 conflict
0xffc921ce…dc0d
0x34b655…2a6f
4 touches
1 conflict
0x0d302116…113e
0x34b655…2a6f
2 touches
0 conflicts
0x0ec07cf7…c0c9
0x34b655…2a6f
2 touches
0 conflicts
0x121f33a5…66eb
0x34b655…2a6f
2 touches
0 conflicts
0x2150ba4f…0742
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 0x74b835e15e…e9b1bd
Audit this contract →
← previous block·next block →recent activity