← previous blocknext block →recent activity
Analyzing
Block #102,642,099
23 transactions · 20 stateful · 2026-09-07 03:05:31 UTC
Parallelism
83/100
Blocked
45%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,642,099 · 23 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
1w02w13w24w35w06w17w08w110w118w219w322w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2f8c65c…4dfe
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0xb58ed141…c32e
0x34b655…2a6f
8 touches
6 conflicts
0x48a9b35f…e5a3
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x67043b0b…97d7
0x34b655…2a6f
6 touches
3 conflicts
0x67c1f465…38b3
0x34b655…2a6f
6 touches
3 conflicts
0x6c7c1a4b…5751
0x34b655…2a6f
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: Perpl
6 conflicts on slot 0xe2f8c65ce8…e14dfe
Audit this contract →
← previous block·next block →recent activity