← previous blocknext block →recent activity
Analyzing
Block #102,484,512
16 transactions · 15 stateful · 2026-09-06 13:47:09 UTC
Parallelism
88/100
Blocked
33%
Avg conflicts / tx
0.31
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,484,512 · 16 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
1w04w15w110w011w112w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xedefe2cc…29d4
0x34b655…2a6f
4 touches
1 conflict
0x4d5053d1…3b7d
0x34b655…2a6f
4 touches
1 conflict
0x60a536a6…ef7a
0x34b655…2a6f
4 touches
1 conflict
0x8c089dae…67c9
0x34b655…2a6f
4 touches
1 conflict
0x982fb529…8be8
0x34b655…2a6f
4 touches
1 conflict
0x9a8af3c2…e4ae
0x34b655…2a6f
4 touches
1 conflict
0xabb9dd5a…5b5f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
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 0xedefe2cc78…1a29d4
Audit this contract →
← previous block·next block →recent activity