← previous blocknext block →recent activity
Analyzing
Block #102,810,489
20 transactions · 16 stateful · 2026-09-07 17:15:49 UTC
Parallelism
70/100
Blocked
44%
Avg conflicts / tx
0.6
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,810,489 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w06w18w113w215w217w318w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xd1203697…1ae0
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xd874dcbe…381c
0x34b655…2a6f
4 touches
1 conflict
0xf407a637…7cc0
0x34b655…2a6f
4 touches
1 conflict
0xd08db6ee…a943
0x40c49f…2af0
4 touches
1 conflict
0xaeb5864c…7679
0x2a68ba…90c5
4 touches
1 conflict
0xe734e4de…02d8
0x40c49f…2af0
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity