← previous blocknext block →recent activity
Analyzing
Block #102,268,829
19 transactions · 19 stateful · 2026-09-05 19:34:26 UTC
Parallelism
68/100
Blocked
32%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,268,829 · 19 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
3w05w18w09w014w115w216w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0xfd4e632c…e14c
0x34b655…2a6f
4 touches
1 conflict
0x50b4806e…c048
0x3bd359…433a
4 touches
1 conflict
0x00000000…0003
0x0c428e…07a4
4 touches
1 conflict
0x20b50479…b75c
0x0158ab…1a70
4 touches
1 conflict
0x00000000…0000
0x0c428e…07a4
4 touches
1 conflict
0x0d2d23d3…8a3a
0x34b655…2a6f
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity