← previous blocknext block →recent activity
Analyzing
Block #102,671,614
11 transactions · 11 stateful · 2026-09-07 05:34:00 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,671,614 · 11 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
1w04w17w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x736b9166…5ea5
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xb5d764c5…c04e
0x34b655…2a6f
4 touches
1 conflict
0x16689b47…a200
0x34b655…2a6f
2 touches
0 conflicts
0x4d803b96…a832
0x34b655…2a6f
2 touches
0 conflicts
0x65ff54af…aa01
0x34b655…2a6f
2 touches
0 conflicts
0x898d9b8a…d1ef
0x34b655…2a6f
2 touches
0 conflicts
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 0x736b916691…db5ea5
Audit this contract →
← previous block·next block →recent activity