← previous blocknext block →recent activity
Analyzing
Block #102,006,487
16 transactions · 15 stateful · 2026-09-04 21:24:55 UTC
Parallelism
56/100
Blocked
40%
Avg conflicts / tx
0.63
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,006,487 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w27w38w49w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xd07b013b…90cb
0x34b655…2a6f
6 touches
3 conflicts
0x75044798…544c
0x34b655…2a6f
6 touches
3 conflicts
0x74b835e1…b1bd
0x34b655…2a6f
6 touches
3 conflicts
0x5c7b5ec0…0764
0x34b655…2a6f
4 touches
1 conflict
0x6823c28e…594c
0x34b655…2a6f
4 touches
1 conflict
0x79ec4509…1f61
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
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