← previous blocknext block →recent activity
Analyzing
Block #102,235,102
16 transactions · 16 stateful · 2026-09-05 16:43:26 UTC
Parallelism
88/100
Blocked
25%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,235,102 · 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
5w06w18w09w110w011w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe3a5c9f0…d17b
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x0b98ef37…7c44
0x34b655…2a6f
2 touches
0 conflicts
0x14ea9ada…e627
0x34b655…2a6f
2 touches
0 conflicts
0x14ea9ada…e628
0x34b655…2a6f
2 touches
0 conflicts
0x6183ee9a…21b1
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 0xe3a5c9f0a8…16d17b
Audit this contract →
← previous block·next block →recent activity