← previous blocknext block →recent activity
Analyzing
Block #102,314,001
18 transactions · 16 stateful · 2026-09-05 23:23:22 UTC
Parallelism
72/100
Blocked
31%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,314,001 · 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
4w05w16w212w313w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65ff54af…aa01
0x34b655…2a6f
10 touches
10 conflicts
0x9ac0202c…196f
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd911522b…e960
0x34b655…2a6f
4 touches
1 conflict
0x25957369…c648
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x75650dc7…d8d7
0x34b655…2a6f
3 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 0x65ff54af45…13aa01
Audit this contract →
← previous block·next block →recent activity