← previous blocknext block →recent activity
Analyzing
Block #102,249,245
19 transactions · 19 stateful · 2026-09-05 17:55:10 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
1.32
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,249,245 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w28w09w110w211w313w314w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0x9d017b93…8081
0x34b655…2a6f
8 touches
6 conflicts
0xc636cc64…b14e
0x34b655…2a6f
6 touches
3 conflicts
0xd29e547b…a1dd
0x34b655…2a6f
4 touches
1 conflict
0xe3849d5f…c6b1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity