← previous blocknext block →recent activity
Analyzing
Block #102,478,962
58 transactions · 47 stateful · 2026-09-06 13:19:02 UTC
Parallelism
84/100
Blocked
57%
Avg conflicts / tx
1.48
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #102,478,962 · 58 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w09w111w012w113w214w015w018w120w121w122w024w025w126w227w334w135w241w244w348w149w251w354w455w556w657w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0xfd4e632c…e14c
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x5f77d607…2c84
0x065c9d…c394
6 touches
3 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: 0xf5b5f7f8…a36d70
36 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity