← previous blocknext block →recent activity
Analyzing
Block #102,064,500
18 transactions · 17 stateful · 2026-09-05 02:18:39 UTC
Parallelism
83/100
Blocked
24%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,064,500 · 18 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
1w02w13w04w113w014w217w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb041f2a8…a44a
0x34b655…2a6f
6 touches
3 conflicts
0x95523e2a…4c01
0x065c9d…c394
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x01315072…0e2d
0x34b655…2a6f
4 touches
1 conflict
0x045532dd…4b7d
0x34b655…2a6f
4 touches
1 conflict
0x0b9d0dba…872d
0x34b655…2a6f
4 touches
1 conflict
0x253fcd81…613c
0x34b655…2a6f
4 touches
1 conflict
0x30c777f3…bacc
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
3 conflicts on slot 0xb041f2a83b…6ea44a
Audit this contract →
← previous block·next block →recent activity