← previous blocknext block →recent activity
Analyzing
Block #102,015,877
25 transactions · 20 stateful · 2026-09-04 22:12:25 UTC
Parallelism
84/100
Blocked
45%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,015,877 · 25 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
1w02w13w27w110w011w116w017w119w020w221w122w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a1711ab…1ee8
0x34b655…2a6f
8 touches
6 conflicts
0xf173eac8…b4ed
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x61a11641…fef0
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x5363946e…9f68
0x34b655…2a6f
4 touches
1 conflict
0x53e08444…d671
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 0x3a1711ab90…521ee8
Audit this contract →
← previous block·next block →recent activity