← previous blocknext block →recent activity
Analyzing
Block #102,057,741
18 transactions · 18 stateful · 2026-09-05 01:44:24 UTC
Parallelism
72/100
Blocked
44%
Avg conflicts / tx
0.89
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,057,741 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w39w012w113w216w017w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x173b64af…6c43
0x34b655…2a6f
8 touches
6 conflicts
0x4dffc33e…068d
0x34b655…2a6f
8 touches
6 conflicts
0x0ec07cf7…c0c9
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0xa2c04336…e4c0
0x34b655…2a6f
8 touches
6 conflicts
0x3d13406e…eff1
0x34b655…2a6f
8 touches
6 conflicts
0xd4f6a526…ad10
0x34b655…2a6f
8 touches
6 conflicts
0xddf10453…d774
0x34b655…2a6f
8 touches
6 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 0x173b64af39…0f6c43
Audit this contract →
← previous block·next block →recent activity