← previous blocknext block →recent activity
Analyzing
Block #102,694,421
18 transactions · 18 stateful · 2026-09-07 07:28:44 UTC
Parallelism
72/100
Blocked
39%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,694,421 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w17w211w312w413w416w117w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xfaf5fe80…1ffc
0x34b655…2a6f
4 touches
1 conflict
0x014e90b3…470f
0x34b655…2a6f
4 touches
1 conflict
0x0513ad6a…3c2a
0x34b655…2a6f
4 touches
1 conflict
0x2c2340c4…bf77
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x69e7ef29…9a4c
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity