← previous blocknext block →recent activity
Analyzing
Block #102,018,499
12 transactions · 12 stateful · 2026-09-04 22:25:40 UTC
Parallelism
42/100
Blocked
58%
Avg conflicts / tx
1.83
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,018,499 · 12 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w27w28w39w410w511w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
14 touches
21 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x7dd96c96…7335
0x34b655…2a6f
10 touches
10 conflicts
0xc0a1a413…6639
0x34b655…2a6f
8 touches
6 conflicts
0xa96f93f2…11f6
0x34b655…2a6f
5 touches
3 conflicts
0xc852b267…9d14
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
21 conflicts on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity