← previous blocknext block →recent activity
Analyzing
Block #104,870,540
29 transactions · 28 stateful · 2026-09-14 22:50:00 UTC
Parallelism
72/100
Blocked
57%
Avg conflicts / tx
1.48
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #104,870,540 · 29 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w17w18w09w010w113w014w115w216w317w418w520w622w123w124w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c68d10b…8386
0x34b655…2a6f
16 touches
28 conflicts
0x42522e76…2592
0x34b655…2a6f
12 touches
15 conflicts
0x9210e826…1414
0x34b655…2a6f
12 touches
15 conflicts
0x86bbab41…5590
0x34b655…2a6f
12 touches
15 conflicts
0x8eb4c866…f05e
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xe783dfa4…5497
0x1b6862…e19c
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
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: Perpl
28 conflicts on slot 0x7c68d10b83…628386
Audit this contract →
← previous block·next block →recent activity