← previous blocknext block →recent activity
Analyzing
Block #102,446,253
13 transactions · 11 stateful · 2026-09-06 10:33:10 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,446,253 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
8w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc282b3d…e139
0x34b655…2a6f
4 touches
1 conflict
0x09b717c6…dbac
0x34b655…2a6f
4 touches
1 conflict
0x9e70dadd…810d
0x34b655…2a6f
4 touches
1 conflict
0x9e70dadd…810e
0x34b655…2a6f
4 touches
1 conflict
0x5b857ef4…4ed8
0x34b655…2a6f
3 touches
1 conflict
0x74e485b1…d380
0x34b655…2a6f
2 touches
0 conflicts
0x75a69dd9…8f57
0x34b655…2a6f
2 touches
0 conflicts
0x9f90e86c…ece7
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0xcc282b3d26…31e139
Audit this contract →
← previous block·next block →recent activity