← previous blocknext block →recent activity
Analyzing
Block #102,325,028
32 transactions · 31 stateful · 2026-09-06 00:19:11 UTC
Parallelism
84/100
Blocked
35%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,325,028 · 32 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
1w02w13w26w37w49w010w111w216w117w018w119w220w331w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x544ac270…ab6b
0x3bd359…433a
8 touches
6 conflicts
0x59d7c788…d068
0x3bd359…433a
8 touches
6 conflicts
0xe0659a3f…90d9
0x000000…a032
8 touches
6 conflicts
0xb45f1840…4a47
0x188d58…ea8e
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
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: Wrapped MON (WMON)
6 conflicts on slot 0x544ac27000…59ab6b
Audit this contract →
← previous block·next block →recent activity