← previous blocknext block →recent activity
Analyzing
Block #102,737,264
9 transactions · 8 stateful · 2026-09-07 11:04:18 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,737,264 · 9 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
4w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba16ea04…3167
0x34b655…2a6f
4 touches
1 conflict
0x2a95b768…2d9d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x39ccd26a…4654
0x34b655…2a6f
4 touches
1 conflict
0x1fb8364c…c10d
0x34b655…2a6f
2 touches
0 conflicts
0x229d2b7e…abdf
0x34b655…2a6f
2 touches
0 conflicts
0x23c8c8dd…7a42
0x34b655…2a6f
2 touches
0 conflicts
0x309f47c0…e1cf
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 0xba16ea0454…063167
Audit this contract →
← previous block·next block →recent activity