← previous blocknext block →recent activity
Analyzing
Block #102,109,513
20 transactions · 19 stateful · 2026-09-05 06:07:05 UTC
Parallelism
60/100
Blocked
37%
Avg conflicts / tx
0.9
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,109,513 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w19w215w316w417w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x7aad02c6…b979
0x34b655…2a6f
8 touches
6 conflicts
0xb5cddf91…0abf
0x34b655…2a6f
6 touches
3 conflicts
0x25ec781a…dca9
0x34b655…2a6f
6 touches
3 conflicts
0x84849074…1ca2
0x34b655…2a6f
5 touches
3 conflicts
0xced4ddba…d164
0x34b655…2a6f
4 touches
1 conflict
0xbf077403…b465
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
10 conflicts on slot 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity