← previous blocknext block →recent activity
Analyzing
Block #102,282,968
12 transactions · 12 stateful · 2026-09-05 20:46:11 UTC
Parallelism
83/100
Blocked
25%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,282,968 · 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
1w02w19w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf1e5e13e…53f3
0x34b655…2a6f
4 touches
1 conflict
0xb637bebe…4cf9
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd02ebff8…fe31
0x34b655…2a6f
4 touches
1 conflict
0xe561281f…7569
0x34b655…2a6f
4 touches
1 conflict
0x0a2131b3…455e
0x34b655…2a6f
4 touches
1 conflict
0x1dc71894…1884
0x34b655…2a6f
4 touches
1 conflict
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 0xf1e5e13eb4…7b53f3
Audit this contract →
← previous block·next block →recent activity