← previous blocknext block →recent activity
Analyzing
Block #102,383,783
20 transactions · 19 stateful · 2026-09-06 05:16:52 UTC
Parallelism
80/100
Blocked
47%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,383,783 · 20 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
1w02w13w04w15w27w19w010w113w015w117w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd713bab…a651
0x34b655…2a6f
6 touches
3 conflicts
0x2f17174f…68b4
0x34b655…2a6f
6 touches
3 conflicts
0x30c777f3…bacc
0x34b655…2a6f
6 touches
3 conflicts
0x4b9b818c…ee64
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x67043b0b…97d7
0x34b655…2a6f
6 touches
3 conflicts
0x7e273bc0…5dbc
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
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
3 conflicts on slot 0xfd713bab1a…98a651
Audit this contract →
← previous block·next block →recent activity