← previous blocknext block →recent activity
Analyzing
Block #102,018,966
11 transactions · 11 stateful · 2026-09-04 22:28:02 UTC
Parallelism
73/100
Blocked
45%
Avg conflicts / tx
0.64
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,018,966 · 11 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
1w02w13w26w18w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffc921ce…dc0d
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x1513b999…b52e
0x34b655…2a6f
4 touches
1 conflict
0x1dc71894…1884
0x34b655…2a6f
4 touches
1 conflict
0x3167d7d8…a06b
0x34b655…2a6f
4 touches
1 conflict
0x3fb3f2e2…fef3
0x34b655…2a6f
4 touches
1 conflict
0x7fd951f1…fe49
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
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 0xffc921ce0e…2adc0d
Audit this contract →
← previous block·next block →recent activity