← previous blocknext block →recent activity
Analyzing
Block #102,020,589
11 transactions · 11 stateful · 2026-09-04 22:36:15 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,020,589 · 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
2w07w18w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0b009709…9b7f
0x11ed3b…2c96
2 touches
0 conflicts
0x982ba7f1…e834
0x11ed3b…2c96
2 touches
0 conflicts
0xab2f6eed…254a
0x188d58…ea8e
2 touches
0 conflicts
0xab2f6eed…254b
0x188d58…ea8e
2 touches
0 conflicts
0xa6b3a7f4…c0e4
0x350035…7777
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity