← previous blocknext block →recent activity
Analyzing
Block #102,861,449
28 transactions · 26 stateful · 2026-09-07 21:32:20 UTC
Parallelism
93/100
Blocked
8%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,861,449 · 28 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
5w010w127w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0x5ad5e6de…e7ad
0x34b655…2a6f
4 touches
1 conflict
0xb8a4b8a7…e631
0x34b655…2a6f
4 touches
1 conflict
0xbc8fb280…76a3
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x62811193…1868
0x34ae4d…3fc5
2 touches
0 conflicts
0x80caf0f7…f2de
0x34ae4d…3fc5
2 touches
0 conflicts
0xd2523794…8a21
0x34ae4d…3fc5
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 0xe1c4e5ce15…770dec
Audit this contract →
← previous block·next block →recent activity