← previous blocknext block →recent activity
Analyzing
Block #102,048,051
17 transactions · 15 stateful · 2026-09-05 00:55:19 UTC
Parallelism
82/100
Blocked
27%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,048,051 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w111w013w115w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0dd39b38…6216
0x34b655…2a6f
4 touches
1 conflict
0x0ec07cf7…c0c9
0x34b655…2a6f
4 touches
1 conflict
0x173b64af…6c43
0x34b655…2a6f
4 touches
1 conflict
0x19f8e68c…4f86
0x34b655…2a6f
4 touches
1 conflict
0x1d821a69…b822
0x34b655…2a6f
4 touches
1 conflict
0x38427ea9…26e1
0x34b655…2a6f
4 touches
1 conflict
0x3d13406e…eff1
0x34b655…2a6f
4 touches
1 conflict
0x4113c42b…5765
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 0x0dd39b3891…776216
Audit this contract →
← previous block·next block →recent activity