← previous blocknext block →recent activity
Analyzing
Block #102,048,384
10 transactions · 9 stateful · 2026-09-05 00:57:00 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,048,384 · 10 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
1w02w14w06w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa2c04336…e4c0
0x34b655…2a6f
4 touches
1 conflict
0xb3e293fe…be2e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd0296d65…129a
0x34b655…2a6f
4 touches
1 conflict
0xdb8288e3…7979
0x34b655…2a6f
4 touches
1 conflict
0xf78d76a3…9dd6
0x34b655…2a6f
4 touches
1 conflict
0x173b64af…6c43
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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 0xa2c0433677…f5e4c0
Audit this contract →
← previous block·next block →recent activity