← previous blocknext block →recent activity
Analyzing
Block #102,485,176
31 transactions · 24 stateful · 2026-09-06 13:50:32 UTC
Parallelism
87/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,485,176 · 31 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w08w114w015w116w017w119w221w023w124w025w130w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x31f71c9c…8f63
0x34b655…2a6f
4 touches
1 conflict
0x8a377bad…474b
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x22f10271…841d
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
3 conflicts on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity