← previous blocknext block →recent activity
Analyzing
Block #102,280,313
19 transactions · 17 stateful · 2026-09-05 20:32:42 UTC
Parallelism
79/100
Blocked
35%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,280,313 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w16w27w38w09w115w118w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xbc2c3cec…7946
0x065c9d…c394
4 touches
1 conflict
0x0b4cd231…59cb
0x34b655…2a6f
4 touches
1 conflict
0x20be46b9…9394
0x34b655…2a6f
4 touches
1 conflict
0x228cce4c…124a
0x34b655…2a6f
4 touches
1 conflict
0x28497968…fc96
0x34b655…2a6f
4 touches
1 conflict
0x2acf7e76…bbe8
0x34b655…2a6f
4 touches
1 conflict
0x354f543b…9fad
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity