← previous blocknext block →recent activity
Analyzing
Block #102,053,097
14 transactions · 11 stateful · 2026-09-05 01:20:53 UTC
Parallelism
79/100
Blocked
45%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,053,097 · 14 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
1w02w14w09w110w212w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x19f8e68c…4f86
0x34b655…2a6f
4 touches
1 conflict
0x25ec781a…dca9
0x34b655…2a6f
4 touches
1 conflict
0x2e957c13…4777
0x34b655…2a6f
4 touches
1 conflict
0x41c56387…a8f6
0x34b655…2a6f
4 touches
1 conflict
0x477cb4f5…11b4
0x34b655…2a6f
4 touches
1 conflict
0x4f3cc09a…2804
0x34b655…2a6f
4 touches
1 conflict
0x5a546b6b…3035
0x34b655…2a6f
4 touches
1 conflict
0x65f011a5…bc6e
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 0x19f8e68cb7…a24f86
Audit this contract →
← previous block·next block →recent activity