← previous blocknext block →recent activity
Analyzing
Block #104,333,515
18 transactions · 17 stateful · 2026-09-13 01:28:50 UTC
Parallelism
83/100
Blocked
24%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #104,333,515 · 18 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
4w010w111w212w015w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6742c574…dbda
0x34b655…2a6f
6 touches
3 conflicts
0xe0e00683…e335
0x34b655…2a6f
6 touches
3 conflicts
0xcb0221be…c2b3
0x34b655…2a6f
6 touches
3 conflicts
0xb0d9297f…aa4b
0x34b655…2a6f
6 touches
3 conflicts
0xea559e7b…41f4
0x34b655…2a6f
4 touches
1 conflict
0x23a320fb…cbd7
0x34b655…2a6f
4 touches
1 conflict
0x4147b177…c9ba
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
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 0x6742c574e1…52dbda
Audit this contract →
← previous block·next block →recent activity