← previous blocknext block →recent activity
Analyzing
Block #102,530,725
16 transactions · 14 stateful · 2026-09-06 17:41:38 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,530,725 · 16 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
1w02w19w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf173eac8…b4ed
0x34b655…2a6f
4 touches
1 conflict
0x0dbecab4…d53e
0x34b655…2a6f
4 touches
1 conflict
0x173b64af…6c43
0x34b655…2a6f
4 touches
1 conflict
0x2e0d8f5c…e70e
0x34b655…2a6f
4 touches
1 conflict
0x3a1711ab…1ee8
0x34b655…2a6f
4 touches
1 conflict
0x50254ee0…e2ea
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x65f011a5…bc6e
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
1 conflict on slot 0xf173eac816…86b4ed
Audit this contract →
← previous block·next block →recent activity