← previous blocknext block →recent activity
Analyzing
Block #102,694,335
17 transactions · 15 stateful · 2026-09-07 07:28:18 UTC
Parallelism
88/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,694,335 · 17 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
2w03w111w014w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26c599c1…706c
0x34b655…2a6f
4 touches
1 conflict
0x3fb3f2e2…fef3
0x34b655…2a6f
4 touches
1 conflict
0x451e482b…7e7d
0x34b655…2a6f
4 touches
1 conflict
0x4b024b98…8f37
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x54379e71…5bf0
0x34b655…2a6f
4 touches
1 conflict
0x63059a8c…e608
0x34b655…2a6f
4 touches
1 conflict
0x6712cb37…06d0
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 0x26c599c1f2…9c706c
Audit this contract →
← previous block·next block →recent activity