← previous blocknext block →recent activity
Analyzing
Block #102,275,062
78 transactions · 76 stateful · 2026-09-05 20:06:02 UTC
Parallelism
97/100
Blocked
4%
Avg conflicts / tx
0.04
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,275,062 · 78 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
1w02w15w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33b7fbba…64de
0x34b655…2a6f
4 touches
1 conflict
0x3cb7ee74…b8a5
0x34b655…2a6f
4 touches
1 conflict
0x403bad45…582b
0x34b655…2a6f
4 touches
1 conflict
0x738d841d…3c29
0x34b655…2a6f
4 touches
1 conflict
0xb9a0dde5…9e2b
0x34b655…2a6f
4 touches
1 conflict
0xca544518…82c2
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd02ebff8…fe31
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
1 conflict on slot 0x33b7fbba1a…5e64de
Audit this contract →
← previous block·next block →recent activity