← previous blocknext block →recent activity
Analyzing
Block #102,326,106
13 transactions · 13 stateful · 2026-09-06 00:24:39 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,326,106 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w09w110w211w312w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa242e227…2e45
0x34b655…2a6f
8 touches
6 conflicts
0xd508719c…3f4e
0x34b655…2a6f
8 touches
6 conflicts
0x76efc1cc…4488
0x34b655…2a6f
8 touches
6 conflicts
0xa9988419…9f45
0x34b655…2a6f
8 touches
6 conflicts
0xb6fcbbb7…2b31
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xfa324e43…8895
0x1b6862…e19c
4 touches
1 conflict
0x100812e9…12b7
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 0xa242e227ce…082e45
Audit this contract →
← previous block·next block →recent activity