← previous blocknext block →recent activity
Analyzing
Block #102,407,463
39 transactions · 24 stateful · 2026-09-06 07:16:48 UTC
Parallelism
90/100
Blocked
42%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,407,463 · 39 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w19w012w013w114w015w016w124w126w227w128w232w334w035w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65ff54af…aa01
0x34b655…2a6f
6 touches
3 conflicts
0xdaadd700…d800
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb83
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4d803b96…a832
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
3 conflicts on slot 0x65ff54af45…13aa01
Audit this contract →
← previous block·next block →recent activity