← previous blocknext block →recent activity
Analyzing
Block #102,253,180
21 transactions · 21 stateful · 2026-09-05 18:15:06 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,253,180 · 21 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
1w02w17w210w011w113w014w215w316w418w019w120w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x73d62b4d…1bec
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6426
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x731d7308…fd26
0x34b655…2a6f
6 touches
3 conflicts
0xdb95e18e…c73e
0x1b6862…e19c
4 touches
1 conflict
0x03f717cd…62de
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 0x73d62b4dd1…c51bec
Audit this contract →
← previous block·next block →recent activity