← previous blocknext block →recent activity
Analyzing
Block #102,068,798
16 transactions · 16 stateful · 2026-09-05 02:40:33 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,068,798 · 16 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
2w03w14w28w29w310w413w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe12f1c48…6322
0x34b655…2a6f
6 touches
3 conflicts
0x9c088939…ddd7
0x34b655…2a6f
6 touches
3 conflicts
0x9d7ac3b9…22f8
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd4f6a526…ad10
0x34b655…2a6f
6 touches
3 conflicts
0x0ec07cf7…c0c9
0x34b655…2a6f
6 touches
3 conflicts
0x477cb4f5…11b4
0x34b655…2a6f
6 touches
3 conflicts
0x4c9b66e1…e999
0x34b655…2a6f
6 touches
3 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
3 conflicts on slot 0xe12f1c48a7…b06322
Audit this contract →
← previous block·next block →recent activity