← previous blocknext block →recent activity
Analyzing
Block #102,282,951
35 transactions · 33 stateful · 2026-09-05 20:46:06 UTC
Parallelism
86/100
Blocked
36%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,282,951 · 35 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
2w03w16w07w18w09w117w220w022w223w324w425w026w127w029w130w131w232w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d1b72ee…6b78
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xa472d565…9fe4
0x3bd359…433a
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x0ba11fca…d413
0x34b655…2a6f
4 touches
1 conflict
0x103da1c1…ded1
0x34b655…2a6f
4 touches
1 conflict
0x146d2fb6…e2e7
0x34b655…2a6f
4 touches
1 conflict
0x2d94ecd9…43db
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 0x6d1b72eefe…416b78
Audit this contract →
← previous block·next block →recent activity