← previous blocknext block →recent activity
Analyzing
Block #102,436,656
40 transactions · 30 stateful · 2026-09-06 09:44:42 UTC
Parallelism
63/100
Blocked
60%
Avg conflicts / tx
2.83
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #102,436,656 · 40 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w314w020w021w022w126w127w228w329w430w531w632w733w834w935w1036w1137w1238w1339w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
30 touches
105 conflicts
0x7aad02c6…b979
0x34b655…2a6f
22 touches
55 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
22 touches
55 conflicts
0xb5cddf91…0abf
0x34b655…2a6f
22 touches
55 conflicts
0xc6f3c5a3…3faa
0x34b655…2a6f
10 touches
10 conflicts
0x3af0dd8e…0024
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 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
105 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity