← previous blocknext block →recent activity
Analyzing
Block #102,205,840
19 transactions · 15 stateful · 2026-09-05 14:15:20 UTC
Parallelism
84/100
Blocked
40%
Avg conflicts / tx
0.58
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,205,840 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w16w07w213w014w115w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x113a6203…5dd8
0x34b655…2a6f
6 touches
3 conflicts
0x5b0621ee…3c2c
0x284f45…7777
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x44ed742f…63f5
0x3bd359…433a
6 touches
3 conflicts
0x4eb758b8…b13b
0x3bd359…433a
6 touches
3 conflicts
0xdf409966…6b16
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0004
0x7aed55…0617
6 touches
3 conflicts
0xa164d951…1534
0xe1c8b7…3022
6 touches
3 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
3 conflicts on slot 0x113a62038a…805dd8
Audit this contract →
← previous block·next block →recent activity