← previous blocknext block →recent activity
Analyzing
Block #102,066,087
22 transactions · 13 stateful · 2026-09-05 02:26:41 UTC
Parallelism
86/100
Blocked
31%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,066,087 · 22 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
1w05w18w09w110w219w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5dc501b…8313
0x34b655…2a6f
6 touches
3 conflicts
0xdbadf6b0…43b2
0x33176b…e078
4 touches
1 conflict
0xb9a0dde5…9e2b
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0xa2eaf598…2cb0
0x34b655…2a6f
4 touches
1 conflict
0x65f011a5…bc6e
0x34b655…2a6f
2 touches
0 conflicts
0x7c216fca…20cb
0x34b655…2a6f
2 touches
0 conflicts
0x7daf6443…fd36
0x34b655…2a6f
2 touches
0 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 0xf5dc501bf7…748313
Audit this contract →
← previous block·next block →recent activity