← previous blocknext block →recent activity
Analyzing
Block #102,398,309
23 transactions · 19 stateful · 2026-09-06 06:30:25 UTC
Parallelism
74/100
Blocked
47%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,398,309 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w16w07w18w29w310w116w417w518w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22f10271…841d
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x3d71b1de…c373
0x34b655…2a6f
6 touches
3 conflicts
0xcb45d9d6…cb82
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x74f672f1…8918
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
6 conflicts on slot 0x22f10271ce…96841d
Audit this contract →
← previous block·next block →recent activity