← previous blocknext block →recent activity
Analyzing
Block #102,406,834
43 transactions · 23 stateful · 2026-09-06 07:13:38 UTC
Parallelism
88/100
Blocked
39%
Avg conflicts / tx
0.33
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,406,834 · 43 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w08w09w010w112w215w016w117w218w128w330w031w434w035w142w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4387ba94…e195
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb83
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0xba478735…26fd
0xd32edf…ff58
5 touches
3 conflicts
0x6d3b7c79…1813
0x34b655…2a6f
4 touches
1 conflict
0x775d7c5e…a0e8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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 0x4387ba941b…8be195
Audit this contract →
← previous block·next block →recent activity