← previous blocknext block →recent activity
Analyzing
Block #102,049,631
18 transactions · 17 stateful · 2026-09-05 01:03:18 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,049,631 · 18 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
2w03w04w110w015w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3623900f…1c70
0x34b655…2a6f
6 touches
3 conflicts
0x91b13e91…855d
0x34b655…2a6f
6 touches
3 conflicts
0xddf10453…d774
0x34b655…2a6f
4 touches
1 conflict
0x67043b0b…97d7
0x34b655…2a6f
4 touches
1 conflict
0x7e273bc0…5dbc
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0xa1a01ded…c087
0x34b655…2a6f
4 touches
1 conflict
0xbb9ab337…f4ec
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
3 conflicts on slot 0x3623900ff9…f51c70
Audit this contract →
← previous block·next block →recent activity